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 So you have an ext4 filesystem in file.img, on top of an ext4 filesystem on /dev/sdb1? > The problem visible only for big images f.x. 160Gb and more. > I did the tests on different hardwares, but result the same. [...] How is test.img created, before you run mkfs? Is it a sparse file or does it have all data blocks allocated? Have you tested this on any other kernel versions (earlier or later)? If not, can you try Linux 3.5, which is available in the experimental suite? Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones.
Attachment:
signature.asc
Description: This is a digitally signed message part