Extending Ext4 LVM Partition

[iyeat]

Greetings,

First of all, I want to preface by saying I have had very bad luck with extending linux filesystems.

My situation is this: I had a 4TB Hardware RAID5 (3x2TB) in a Fedora Box. I use this array for backups, files, music, lots of things.

Recently it started to grow low on space, so I procured a 4th 2TB drive, and added it to the Hardware RAID. No issues with that. The RAID BIOS shows the new ~6TB Capacity.

What I am having trouble doing is making Linux extend it's partition to the ~6TB size.

The RAID is device SDC1.

SDC1 is a member of the volume group vg_3ware.

I'd appreciate some help. All of the tutorials and howtos I've found seem useful, but I always get stuck because i only see the original ~4TB size in Linux, and not the new size.

Thanks!

C

[falko]

Did you check out this guide? http://www.howtoforge.com/linux_lvm

[iyeat]

Falko,

Thanks for the post, I appreciate the time.

I did consult the LVM guide. It's pretty comprehensive.

However, my partition table is using GPT because 6TB is too large for DOS.

Using the guide as a refernce, I was able to make the partition 6TB using parted.

[root@buster ~]# parted /dev/sdc
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                                
Model: AMCC 9590SE-8ML DISK (scsi)
Disk /dev/sdc: 6000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags
 1      17.4kB  6000GB  6000GB               primary

This is great, however using e2fsck gives an error that the device is in use:

[root@buster ~]# sudo e2fsck -f /dev/sdc1
e2fsck 1.41.12 (17-May-2010)
e2fsck: Device or resource busy while trying to open /dev/sdc1
Filesystem mounted or opened exclusively by another program?

I'm not sure if there is a trick to figuring out what is using the device, especially since it's not mounted.

Any advice is much appreciated.

Thanks!

C

[falko]

Have you tried a reboot?