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

Bug#680487: marked as done (bug for formating big size file images)



Your message dated Sat, 24 Apr 2021 06:16:23 -0700 (PDT)
with message-id <60841a27.1c69fb81.b3d7.34cf@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #680487,
regarding bug for formating big size file images
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
680487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680487
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: unidentified (can be kernel, fs-tools, or other)


When I'm trying to format 200Gb empty file image, with the following command:
"mkfs -t ext4 ./file.img"
(file image was created by the following command: "dd bs=1M count=200k
if=/dev/zero of=file.img" )

after some period ot time it is return such messages

[50969.139244] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769:
inode #19922947: comm mkfs.ext4: bad extent address lblock: 303, depth: 2
pblock 0
[50969.139378] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769:
inode #19922947: comm mkfs.ext4: bad extent address lblock: 304, depth: 2
pblock 0
[50969.139510] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769:
inode #19922947: comm mkfs.ext4: bad extent address lblock: 305, depth: 2
pblock 0
[50969.139643] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769:
inode #19922947: comm mkfs.ext4: bad extent address lblock: 306, depth: 2
pblock 0
[50969.139776] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769:
inode #19922947: comm mkfs.ext4: bad extent address lblock: 307, depth: 2
pblock 0
......


the problem is not discovered with small image files, (f.x. <10Gb)

I am using Debian Wheezy 3.2.0-2-amd64 #1 SMP Mon Jun 11 17:24:18 UTC 2012
x86_64 GNU/Linux

no any patches are  installed, all system by default installation.




with debian Squeeze no such poblem was discovered.


Hrayr.







--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---

Reply to: