Bug#613737: e2fsprogs: Programming error? block #33600 claimed for no reason in process_bad_block.
On Mi, Feb 16, 2011 at 05:47:45 -0500, Ted Ts'o wrote: debugfs /dev/sdb6 debugfs: icheck 33600 33637 [...] debugfs: stat 12345 1.41.12 (17-May-2010) debugfs: icheck 33600 33637 Block Inode number 33600 7 33637 7 debugfs: stat 7 7: File not found by ext2_lookup Also, if you retry the e2fsck with the -cc, can you reproduce the problem? I'd rather wait for your response before trying this, because one run takes about 20 hours. Thanks, Johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613737: e2fsprogs: Programming error? block #33600 claimed for no reason in process_bad_block.
On Feb 17, 2011, at 3:02 AM, Johannes Rohr wrote: On Mi, Feb 16, 2011 at 05:47:45 -0500, Ted Ts'o wrote: debugfs /dev/sdb6 debugfs: icheck 33600 33637 [...] debugfs: stat 12345 1.41.12 (17-May-2010) debugfs: icheck 33600 33637 Block Inode number 33600 7 33637 7 debugfs: stat 7 7: File not found by ext2_lookup that should be: debugfs: stat 7 (The angle brackets are important. Otherwise it's looking for the file with the name '7' in the debugfs's idea of the current working directory. You can use commands like 'cd' and 'ls' in debugfs) -- Ted -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613737: e2fsprogs: Programming error? block #33600 claimed for no reason in process_bad_block.
Package: e2fsprogs Version: 1.41.12-2 Severity: normal I have run a full read-write surface scan on an ext4 partition on an external USB hard drive (e2fsck -ccfy /dev/sdb6), which lasted for about 20 hours. After that, e2fsck emits the following error message: Pass 1: Checking inodes, blocks, and sizes Programming error? block #33600 claimed for no reason in process_bad_block. Programming error? block #33637 claimed for no reason in process_bad_block. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information backup: 371156/11919360 files (0.3% non-contiguous), 28357540/47648097 blocks I have absolutely no idea what to make of this. Any ideas? -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990, 'stable'), (500, 'squeeze-updates'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages e2fsprogs depends on: ii e2fslibs 1.41.12-2 ext2/ext3/ext4 file system librari ii libblkid1 2.17.2-9 block device id library ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libcomerr21.41.12-2 common error description library ii libss21.41.12-2 command-line interface parsing lib ii libuuid1 2.17.2-9 Universally Unique ID library ii util-linux2.17.2-9 Miscellaneous system utilities e2fsprogs recommends no packages. Versions of packages e2fsprogs suggests: pn e2fsck-static none (no description available) ii gpart 0.1h-11+b1 Guess PC disk partition table, fin ii parted2.3-5 The GNU Parted disk partition resi -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613737: e2fsprogs: Programming error? block #33600 claimed for no reason in process_bad_block.
On Wed, Feb 16, 2011 at 11:17:58PM +0100, Johannes Rohr wrote: Package: e2fsprogs Version: 1.41.12-2 Severity: normal I have run a full read-write surface scan on an ext4 partition on an external USB hard drive (e2fsck -ccfy /dev/sdb6), which lasted for about 20 hours. After that, e2fsck emits the following error message: First of all, can you map the blocks to specific inodes: debugfs /dev/sdb6 debugfs: icheck 33600 33637 then when you get the inode numbers, can you try using the debugfs stat command and show me the output. i.e., if the inode number is 12345, enter the command: debugfs: stat 12345 Also, if you retry the e2fsck with the -cc, can you reproduce the problem? Finally, if you retry the e2fsck command without the -cc can you reproduce this? (i.e., e2fsck -fy /dev/sdb6). If no, can you try it with the -cc again (e2fsck -ccfy /dev/sdb6). - Ted -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
