On Sun, 2012-08-26 at 00:56 +0400, hrayr@infotech.am wrote: > > On Fri, 2012-08-24 at 03:30 +0400, Hrayr Grigoryan wrote: > >> Package: src:linux > >> Version: 3.2.23-1 > >> Severity: critical > >> Tags: lfs > >> Justification: causes serious data loss > >> > >> Dear Maintainer, > >> > >> When I'm trying to format file image with the command "mkfs -t ext4 > >> file.img", it returns the following errors > >> [ 142.328065] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: > >> inode #12: comm mkfs.ext4: bad extent address lblock: 1022, depth: 2 > >> pblock 0 > >> [ 142.328387] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: > >> inode #12: comm mkfs.ext4: bad extent address lblock: 1023, depth: 2 > >> pblock 0 > >> [ 142.328699] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: > >> inode #12: comm mkfs.ext4: bad extent address lblock: 9254, depth: 2 > >> pblock 0 > >> [ 142.329018] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: > >> inode #12: comm mkfs.ext4: bad extent address lblock: 1057, depth: 2 > >> pblock 0 [...] > > Have you tested this on any other kernel versions (earlier or later)? > Yes, I have tested with the earlier versions, all earlier versions of > 3.x.x kernels have this bug. I talked to the ext4 maintainer about this. He recognised the problem and said you can work around this by adding the option '-E nodiscard' when running mke2fs. This is supposed to be fixed in Linux 3.5.3 (not yet available in Debian). We will try to get it fixed in Linux 3.2.y soon. Ben. -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part