On Aug 23, Bryn M. Reeves transmitted in part:
#resize2fs /dev/vg0/logs ( and it gets screwed up here )
resize2fs 1.39 (29-May-2006) *resize2fs: Filesystem has unsupported
feature(s) while trying to open /dev/vg0/logs* *Couldn't find valid
filesystem superblock.*
This is the problem. You appear to be using a version of e2fsprogs
that is older than the version used to create the file system in the
first place. In this case they will give up and refuse to do anything
rather than potentially damage a file system that has unknown features
enabled.
lvm version LVM version: 2.02.88(2)-RHEL5 (2012-01-20) Library
version: 1.02.67-RHEL5 (2011-10-14) Driver version: 4.11.6
Can you post the version of e2fsprogs you have installed and also the
output of "dumpe2fs -h /dev/vg0/logs"?
I can guess pretty confidently what the problem is. RHEL5 supports
ext2 and ext3, but *not* ext4 (unless you install ext4progs, and then
you have to run resize4fs, not resize2fs). But it has a very stable
Xen. The OP probably has a VM that uses ext4, and it trying to resize
the filesystem using the old resize2fs on his RHEL5 dom0.
What the OP *should* do:
1) after extending the LV, shutdown and startup the VM so that it sees
the new size, and run resize2fs in the VM (where it is the right
version and will do an online resize).
or
2) install e4fsprogs in RHEL5, and use resize4fs on dom0
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
