bug when we do an mkfs.ext4 + tune2fs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I have an error when I try to mount an ext4 after having changed its
uuid with tune2fs. If I just do an mkfs.ext4 I can mount it, but if I
do an mkfs.ext4 and then an e2label -U on it, it can't be mounted.
Fortunately this bug is quite easy to reproduce.

1) mkfs.ext4 /dev/xxxx  -b 4096  -I 256 -O
has_journal,ext_attr,resize_inode,dir_index,filetype,extent,flex_bg,sparse_super,large_file,huge_file,uninit_bg,dir_nlink,extra_isize,^journal_dev

2) "mount -t ext4 /dev/xxxx /mnt/test" works

3) umount /dev/xxxx

4) tune2fs /dev/xxxx  -U 19ad8325-2e39-4be1-a6b1-a5d2d1015eeb

5) "mount -t ext4 /dev/xxxx /mnt/test" fails

6) we can see the following error in the log messages
EXT4-fs: ext4_check_descriptors: Checksum for group 0 failed (10987!=27579)
EXT4-fs: group descriptors corrupted!


I am running a 64bit 2.6.27.12 kernel with 64bit binaries, and e2fsprogs-1.41.3.

Another user using Ubuntu jaunty alpha3 on a 32bit system has exactly
the same problem, so it sounds that all recent ext4 versions are
impacted.

The mkfs command is quite long just because the list of filesystem
features have been saved by a tool which must recreate the filesystem
with the same attributes.

Thanks
--
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

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux