https://bugzilla.kernel.org/show_bug.cgi?id=16583 Theodore Tso <tytso@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tytso@xxxxxxx --- Comment #3 from Theodore Tso <tytso@xxxxxxx> 2012-08-13 19:34:25 --- Also, in the original bug report, (which was against an usptream kernel, 2.6.35) note: EXT4-fs (dm-6): warning: mounting fs with errors, running e2fsck is recommended If this means the file system was mounted with inconsistencies noted in the past. And sure enough... EXT4-fs error (device dm-6): ext4_ext_search_left: inode #3510: (comm flush-254:6) ix (42117) != EXT_FIRST_INDEX (0) (depth 1)! ... is a file system inconsistency. The second reporter, Loredan, was using a Red Hat modified 2.6.32 kernel, and the RHEL 2.6.32 kernel is significantly different from upstream. I will note that it wasn't clear whether the file system was being grown or shrunk, but in the more typical case of growing the file system, in general you should resize the LVM first, and *then* run resize2fs to resize the filesystem to use the newly enlarged LV. Regards, -- Ted -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
