topic Re: Extending File System on RHEL 5.5 in Operating System - Linux

Extending File System on RHEL 5.5

Manoj1 — Sun, 13 Feb 2011 21:29:34 GMT

Hi all,

We need to extend file system /opt/pluto by 150 Gigs to a non root volume group assigned file system.

SAN team have provided LUNs on this server.
Can someone elaborate steps to be performed to extend file system here ?

Thanks,
Manoj

Re: Extending File System on RHEL 5.5

Wouter Jagers — Mon, 14 Feb 2011 09:15:31 GMT

Basic steps would be:

Determine volume group + logical volume with df.
Add provided LUN(s) into VG with vgextend.
Enlarge logical volume with lvextend.
Enlarge filesystem with resize2fs.

..assuming that the provided LUN(s) are visible and ready for use.

Cheers
Wout

Re: Extending File System on RHEL 5.5

Ross.Murphy — Mon, 14 Feb 2011 17:05:33 GMT

http://tldp.org/HOWTO/LVM-HOWTO/commontask.html
http://tldp.org/HOWTO/LVM-HOWTO/extendlv.html

Check these articles out. It documents the process of expanding logical volumes very well.

I have used it and it's worked for me.

Hope that helps.

Re: Extending File System on RHEL 5.5

Alzhy — Mon, 14 Feb 2011 21:08:16 GMT

Issue:

/dev/mapper/vgname-lvolname /data is at 99%

How to Increase Filesystem:

vgdisplay vgname
(check if there are free extents to extend the logical volume of the underlying "Filesystem)

lvextend -L +4GB /dev/vgname/volname

resize2fs /dev/vgname/lvolname

ALL done ONLINE without unmounting the filesystem/interrupting I/O.

Now to shrink filesystem ONLINE -- now that is another matter.

HTH.

Re: Extending File System on RHEL 5.5

Manoj1 — Tue, 22 Feb 2011 04:38:04 GMT

If new LUNs are added from HP's disk array to Linux Servers File Systems then how do we find which are new luns and not being used ?

So that we do not accidently use the LUNs which are already being used by the systems.

Re: Extending File System on RHEL 5.5

Matti_Kurkela — Tue, 22 Feb 2011 08:09:25 GMT

If a disk device is already in use by LVM, pvcreate won't run (unless you use -f or -ff, in which case it's your own fault).
Example:

# pvcreate /dev/sdc1
Can't initialize physical volume "/dev/sdc1" of volume group "vg00" without -ff
(Oops, it's already in use. No harm done...)

If you use legacy PC partition tables (= those created by fdisk and similar tools) on your disks, you should notice that the disk already has a partition of type "Linux", "Linux LVM", "Linux raid autodetect" or similar.

If you have multipathing, use whatever tool you have to list all multipathed disks ("multipath -l" for RHEL default device-mapper-multipath; "powermt display" for EMC PowerPath; etc.). Then run "pvs" to see all PVs managed by LVM, and look for disks that are in one list but not in the other.

NOTE: if your site is using any software that uses raw disks, look into the documentation of that software to find out how to identify that a disk is in use by that software. (Because raw disk formats are often proprietary, there is no all-encompassing tool for this.)
Make sure other sysadmins at your site know that identification procedure too.

MK