[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ext2 resize problem
From: |
Andrew Clausen |
Subject: |
Re: ext2 resize problem |
Date: |
Mon, 26 Aug 2002 10:46:37 +1000 |
User-agent: |
Mutt/1.3.28i |
On Sat, Aug 24, 2002 at 12:16:33PM +0100, Phil Williams wrote:
> Hi,
> I have just seen a problem similar to that reported by wen shaohua (on 06 Jun
> 2002 10:38:32 +0800).
>
> Here is the ouput of the command 'parted /dev/hda print':
>
> Disk geometry for /dev/hda: 0.000-58644.140 megabytes
> Disk label type: msdos
> Minor Start End Type Filesystem Flags
> 1 0.031 8.367 primary ext2 boot
> 4 8.367 21000.164 extended lba
> 5 8.398 4104.351 logical ext2
> 6 4104.382 20500.101 logical ext2
> 7 20500.132 20756.039 logical linux-swap
> 3 21000.164 36000.070 primary ext2
> 2 49999.852 53000.226 primary ext2
>
> Using the Parted boot and root (1.6.2) disks (so that no /dev/hda filesystems
> were mounted), I created /dev/hda5 using
>
> mkpartfs logical ext2 8.367 4104.367
>
> and then copied /dev/hda2 using
>
> cp 2 5
>
> So the /dev/hda5 filesystem should be 4GB, but 'df -m' reports:
>
> Filesystem 1M-blocks Used Available Use% Mounted on
> /dev/hda5 2952 1282 1490 47% /
> /dev/hda1 8 3 5 35% /boot
> /dev/hda6 16137 7222 8095 48% /home
>
> I have since tried using the resize command to enlarge the filesystem, but
> that
> had no effect. Do you have any suggestions? Am I doing something wrong?
I can't see any explanation for this... you are doing the right thing.
Obvious question: you didn't have /dev/hda5 mounted while
copying/resizing? (I think you'd have known about it if you were...)
Apart from that, it looks like Parted might be silently failing.
(It shouldn't!)
When you resize, does it show a progress meter? Any funny behaviour?
> I got the following error message from lilo:
>
> LILO version 22.2, Copyright (C) 1992-1998 Werner Almesberger
> Development beyond version 21 Copyright (C) 1999-2001 John Coffman
> Released 05-Feb-2002 and compiled at 20:57:26 on Apr 13 2002.
> MAX_IMAGES = 27
>
> Reading boot sector from /dev/hda
> Merging with /boot/boot.b
> Fatal: open /boot/boot.b: No such file or directory
>
> On my system, /boot/boot.b is a symbolic link to the regular file boot-menu.b
Does that file exist? (Can you open it via /boot/boot.b?)
Cheers,
Andrew