When using ext2prepare to make sure a ext3 file system is online
resizable, e2fsck find errors in the file system after the conversion.
Anyone know what is going on here?
This problem is reported in debian, <URL:http://bugs.debian.org/348778>.
The following commands demonstrate the problem (assuming LVM volume
gorup intern_vg and more than 150 MiB free space on the volume group):
lvcreate -L150 -ntest_lv intern_vg
mke2fs -j /dev/intern_vg/test_lv
ext2prepare /dev/intern_vg/test_lv 500m
e2fsck -y -f /dev/intern_vg/test_lv
This is the output from e2fsck:
# e2fsck -y -f /dev/vg_system/lv_test
e2fsck 1.37 (21-Mar-2005)
Resize inode not valid. Recreate? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -3 +4389 -8195 -24579 -40963 -57347 -73731
Fix? yes
Free blocks count wrong for group #0 (3803, counted=3804).
Fix? yes
Free blocks count wrong for group #1 (7931, counted=7932).
Fix? yes
Free blocks count wrong for group #3 (7931, counted=7932).
Fix? yes
Free blocks count wrong for group #5 (7931, counted=7932).
Fix? yes
Free blocks count wrong for group #7 (7931, counted=7932).
Fix? yes
Free blocks count wrong for group #9 (7931, counted=7932).
Fix? yes
Free blocks count wrong (146599, counted=146605).
Fix? yes
/dev/vg_system/lv_test: ***** FILE SYSTEM WAS MODIFIED *****
/dev/vg_system/lv_test: 11/38912 files (0.0% non-contiguous), 9043/155648 blocks
#
Friendly,
--
Petter Reinholdtsen
|