Have you rebooted since adding the space?
RHEL4 and RHEL5 get somewhat grumpy when you change the size of a SAN device; i have had limited luck forcing a rescan.
does /proc/partitions have the correct size?
Main Topics
Browse All TopicsWe have a redhat linux server with a virtual disk that resides on our SAN. We just added a couple hundred more gigs to the vdisk for the linux server. The SAN knows that we added the space but we cant get Linux to see the change.
The following commands have been used with no luck:
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Heres a rundown of the commands to extend an LVM volume after adding space on the LUN:
(Keep in mind that if you remove the LUN presented as /dev/sdb, the current /dev/sdc device may become /dev/sdb instead. If so, just sub sdb for sdc)
Use fdisk /dev/sdc to create a new partition, and make it type 8e.
(below steps assume you just created /dev/sdc2)
partprobe /dev/sdc
pvcreate /dev/sdc2
vgextend SAN /dev/sdc2
lvextend -l +100%FREE /dev/SAN/oracle
e2fsck -f /dev/SAN/oracle (NOTE: do not run e2fsck on a partition that is currently mounted.)
resize2fs /dev/SAN/oracle
mount /dev/SAN/oracle /oracle
If everything tests out OK, then you can edit /etc/fstab, and remove the # from the last line:
/dev/SAN/oracle /oracle ext3 defaults 1 2
Business Accounts
Answer for Membership
by: it4sohoPosted on 2009-09-30 at 14:17:55ID: 25463744
It looks to me like you've found documentation for LVM1, when you're probably using LVM2.
Try these 2 command lines for use with LVM2:
# lvextend -L+500M /dev/vg0/data
# resize2fs /dev/vg0/data
(At issue -- and in the WTMI department -- is that e2fsadm is a LVM1 command, and there is no equivalent for LVM2. That e2fsadm program is supposed to do the resize of the partition (lvextend) AND the filesystem (resize2fs) at the same time. But it doesn't work on LVM2
PLEASE check your system for LVP packages -- you should be running LVM2 and NOT LVM1! (You may have both if you've upgraded the system or otherwise updated since original install... LVM2 packages should be version 2.02 or later).
Let me know how this works! :-)
Dan
IT4SOHO