Q: Online resizing ext3 FS
Hi I apologize in advance for asking a question not really appropriate for this mailing list, but I couldn't find a better place with lots of people managing lots of disk space. The question: Has anyone of you been using ext2online to resize (large) ext3 filesystems? I have to do it going from 500GB to 1TB on a productive system I was wondering if you have some horror/success stories. I'm using RHEL4/U4 (kernel 2.6.9) on this system. Thanks for your time. Regards, Chris UNIX System Engineer Swisscom Mobile Ltd. Switzerland - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [linux-lvm] Q: Online resizing ext3 FS
I've been fine with it, so long as you have done the ext2prepare before hand. Otherwise you will only be able to go up to the next 16G boundary. I asked it to skip the fsck check but I've been told this is not a good idea -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Osicki Sent: 12 September 2007 15:36 To: linux-raid@vger.kernel.org; [EMAIL PROTECTED] Subject: [linux-lvm] Q: Online resizing ext3 FS Hi I apologize in advance for asking a question not really appropriate for this mailing list, but I couldn't find a better place with lots of people managing lots of disk space. The question: Has anyone of you been using ext2online to resize (large) ext3 filesystems? I have to do it going from 500GB to 1TB on a productive system I was wondering if you have some horror/success stories. I'm using RHEL4/U4 (kernel 2.6.9) on this system. Thanks for your time. Regards, Chris UNIX System Engineer Swisscom Mobile Ltd. Switzerland ___ linux-lvm mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-lvm] Q: Online resizing ext3 FS
Chris Osicki schrieb: Hi I apologize in advance for asking a question not really appropriate for this mailing list, but I couldn't find a better place with lots of people managing lots of disk space. The question: Has anyone of you been using ext2online to resize (large) ext3 filesystems? I have to do it going from 500GB to 1TB on a productive system I was wondering if you have some horror/success stories. I'm using RHEL4/U4 (kernel 2.6.9) on this system. Yes, I tried to online resize a similar filesystem (600 MB to 1.2 TB) and it didn't work. At some point, resize2fs would just exit with errors. I tried to do it several times before I figured out what's missing; sometimes, I interrupted the process with ctrl+c. No data loss occurred. To do an online ext3 resize, the filesystem needs a resize_inode feature. You can check the features with dumpe2fs: # dumpe2fs -h /dev/sda1 (...) Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file (...) This flag is added by default only in the recent versions of e2progs (1.39 and later AFAIR); before, it had to be specified manually. So with RHEL4, you may be out of luck. In the end, I had to to an offline resize. I had this volume mirrored on another machine, so I didn't worry that much though. Also, to resize a filesystem of that size you would need plenty of RAM (if you have about 1 GB RAM free, it should be just enough; otherwise, your machine will be swapping, and the process will take longer). Before, I tried to resize it on a machine with 256 MB and several snapshots; resize2fs was killed because of OOM, and still, no data loss. If you have that an old kernel, take care if you're using snapshots; I believe they are stable only as of 2.6.22 (before 2.6.22 snapshots needed a lot of RAM; before 2.6.18 there were problems with snapshots removing etc.). Would be good to add some of that info to LVM HOWTO. -- Tomasz Chmielewski http://wpkg.org - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [linux-lvm] Q: Online resizing ext3 FS
On Wed, 12 Sep 2007, Hiren Joshi wrote: Has anyone of you been using ext2online to resize (large) ext3 filesystems? I have to do it going from 500GB to 1TB on a productive system I was wondering if you have some horror/success stories. I'm using RHEL4/U4 (kernel 2.6.9) on this system. This brings up an LVM related question I've had. Can I do this: 1) take snapshot of 500GB LV 2) resize source LV to 1TB 3) run ext2online 4a) resize succeeds - remove shapshot 4b) resize fails horribly - copy shapshot to LV and restart 4b.1) is there a way to revert the source LV to the snapshot? (without allocating snapshot as big as source LV) -- Stuart D. Gathman [EMAIL PROTECTED] Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154 Confutatis maledictis, flammis acribus addictis - background song for a Microsoft sponsored Where do you want to go from here? commercial. - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RAID6 mdadm --grow bug?
Problem: The mdadm --grow command fails when trying to add disk to a RAID6. The man page says it can do this. GROW MODE The GROW mode is used for changing the size or shape of an active array. For this to work, the kernel must support the necessary change. Various types of growth are being added dur- ing 2.6 development, including restructuring a raid5 array to have more active devices. Currently the only support available is to · change the size attribute for RAID1, RAID5 and RAID6. · increase the raid-disks attribute of RAID1, RAID5, and RAID6. · add a write-intent bitmap to any array which supports these bitmaps, or remove a write- intent bitmap from such an array. So far I have replicated this problem on RHEL5 and Ubuntu 7.04 running the latest official updates and patches. I have even tried it with the most latest version of mdadm 2.6.3 under RHEL5. RHEL5 uses version 2.5.4. How to replicate the problem: You can either use real physical disks or use the loopback device to create fake disks. Here are the steps using the loopback method as root. cd /tmp dd if=/dev/zero of=rd1 bs=10240 count=10240 cp rd1 rd2;cp rd1 rd3;cp rd1 rd4;cp rd1 rd5 losetup /dev/loop1 rd1;losetup /dev/loop2 rd2;losetup /dev/loop3 rd3;losetup /dev/loop4 rd4;losetup /dev/loop5 rd5 mdadm --create --verbose /dev/md0 --level=6 --raid-devices=4 /dev/ loop1 /dev/loop2 /dev/loop3 /dev/loop4 At this point wait a minute while the raid is being built. mdadm --add /dev/md0 /dev/loop5 mdadm --grow /dev/md0 --raid-devices=5 You should get the following error mdadm: Need to backup 384K of critical section.. mdadm: Cannot set device size/shape for /dev/md0: Invalid argument How to clean up mdadm --stop /dev/md0 mdadm --remove /dev/md0 losetup -d /dev/loop1;losetup -d /dev/loop2;losetup -d /dev/ loop3;losetup -d /dev/loop4;losetup -d /dev/loop5 rm rd1 rd2 rd3 rd4 rd5 David. - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
