Re: [dm-devel] How to Resize Partition

[Gabriel Barazer <gabriel oxeva fr>]

On 02/12/2008 4:30:38 PM +0100, "Scott Moseman" <scmoseman gmail com> wrote:
> This is the original size of my partition, 50GB...
>
> # df -h | grep mpath
> /dev/mapper/mpath0p1   50G  2.1G   45G   5% /san

50G is the size of the mounted filesystem, not related to the block device

> I increased it to 60GB and am trying to resize.  Through my
> troubleshooting and various attempts, I've increased /dev/sdb1 (NIC),
> /dev/sdc1 (HBA) and /dev/mapper/mpath0p1 (MPIO).
>
> Disk /dev/sdb: 64.4 GB, 64424509440 bytes
> /dev/sdb1               1       61440    62914544   83  Linux
>
> Disk /dev/sdc: 64.4 GB, 64424509440 bytes
> /dev/sdc1               1       61440    62914544   83  Linux
>
> Disk /dev/mapper/mpath0: 64.4 GB, 64424509440 bytes
> /dev/mapper/mpath0p1               1       61440    62914544   83  Linux

Here are the block device size, not related with the filesystem mounted 
on top of it.

> I unmount/mount, reboot, etc and the mounted partition keeps showing
> up as 50GB.  How do I get my additional 10GB?  This is on a CentOS 4.5
> server.

You increased the block device size, but not the filesystem. You only 
have to modify the filesystem to take the extra room added into account.
You didn't mentionned what FS you use. For ext2/3 see tune2fs; for 
reiserfs see resize_reiserfs; for XFS (highly recommended! for this kind 
of usage, except if you are using a cluster FS) use xfs_growfs.

Anyway, the device-mapper is aware of the new size (because acting at 
the block-level), but no dm tool can do anything on data (filesystems) 
above the block layer.

For cluster filesystems, you have to check the docs because you cannot 
modify a filesystem without any locking management (or else you will 
cause a big mess in your data). Or maybe you will have to unmount the 
device to do that.

Gabriel