Since I'm not *entirely* sure if this is related to the the extent header
issue[0], I thought I just report it:
When shrinking a filesystem with resize2fs, fsck.ext4 (1.41.3,
12-Oct-2008) reports:
------------
Pass 5: Checking group summary information
Block bitmap differences: -(2488--2493) -(149959--151395)
Fix<y>? yes
Free blocks count wrong for group #0 (3188, counted=3194).
Fix<y>? yes
Free blocks count wrong for group #4 (10182, counted=11619).
Fix<y>? yes
Free blocks count wrong (26225, counted=27668).
Fix<y>? yes
-----------
After this, the filesystem is perfectly fine though, no corruptions have
been noticed yet. I'm even able to mount it without running fsck after the
resize2fs. I've put a few more details here:
http://nerdbynature.de/bits/2.6.28/
Thanks,
Christian.
[0] http://thread.gmane.org/gmane.comp.file-systems.ext4/10736
PS: As my rootfs is also on ext4, I noticed another, completely unrelated oddity:
[ 1.604198] Using IPI Shortcut mode
[ 1.608394] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 1.737198] EXT3-fs: hda1: couldn't mount because of unsupported optional features (240).
[ 1.754302] EXT4-fs: barriers enabled
[ 1.773267] kjournald2 starting. Commit interval 5 seconds
...this is befor INIT starts, so who's trying to mount "/" as ext3 first?
--
BOFH excuse #55:
Plumber mistook routing panel for decorative wall fixture
--
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
