Hi all, I want to setup a linux workstation with FC4 and with all the partitions (except for /boot) under LVM to be able to resize them in future. I don't need online resizing, I can shutdown the system and reboot with the rescuecd when needed. I have done some test on this configuration and I have sverals doubts: If i format a partition with the resize_inode feature enabled and I resize it offline with resize2fs all is ok until I reach (in a single step or in several step) 1000*(Original Size). When i extend a partition over this size I receive a couple of error when I launch fsck.ext3 and the resize_inode feature disappears. If I format a partition without the resize_inode feature then i can resize it to any size, but after the resize the first launch of fsck.ext3 gives always this error: Backing up journal inode block information In both the scenarios after the resize I'm able to mount the partitions. The question is: for offline resizing is better to diseble the resize_inode feature ? Is the error message i wrote really an error ? jjletho P.S. I'm sorry but at the moment the subscription form does not work so if you can put me in cc... ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it
Hi all, I want to setup a linux workstation with FC4 and with all the partitions (except for /boot) under LVM to be able to resize them in future. I don't need online resizing, I can shutdown the system and reboot with the rescuecd when needed. I have done some test on this configuration and I have sverals doubts: If i format a partition with the resize_inode feature enabled and I resize it offline with resize2fs all is ok until I reach (in a single step or in several step) 1000*(Original Size). When i extend a partition over this size I receive a couple of error when I launch fsck.ext3 and the resize_inode feature disappears. If I format a partition without the resize_inode feature then i can resize it to any size, but after the resize the first launch of fsck.ext3 gives always this error: Backing up journal inode block information In both the scenarios after the resize I'm able to mount the partitions. The question is: for offline resizing is better to disable the resize_inode feature ? Is the error message i wrote really an error ? jjletho ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it
Possibly Parallel Threads
- clone RHEL 4 ext3 partition
- Ghost 8.0 Clone Filesystem with ext3 (remove resize_inode and ext_attr features)
- Filesystem won't mount because of "unsupported optional features (80)"
- Re-sizing qcow2 images
- resize2fs on LVM on MD raid on Fedora Core 3 - inode table conflicts in fsck