linux-kernel - Re: Severe data corruption with ext4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Mar 2009 10:10:43 +0100
From:	Richard <richard@...elected.de>
To:	Theodore Tso <tytso@....edu>, linux-kernel@...r.kernel.org,
	linux-ext4@...r.kernel.org
Subject: Re: Severe data corruption with ext4

On Mon, Mar 23, 2009 at 03:05, Theodore Tso <tytso@....edu> wrote:
> On Fri, Mar 20, 2009 at 10:44:02AM +0100, Richard wrote:

>> Mar 22 13:47:33 bakunin kernel: __find_get_block_slow() failed.
>> block=197478301302784, b_blocknr=0
>> Mar 22 13:47:33 bakunin kernel: b_state=0x00188021, b_size=4096
>> Mar 22 13:47:33 bakunin kernel: device blocksize: 4096
>> Mar 22 13:47:33 bakunin kernel: __find_get_block_slow() failed.
>> block=197478301302784, b_blocknr=0
>> Mar 22 13:47:33 bakunin kernel: b_state=0x00188021, b_size=4096
>> Mar 22 13:47:33 bakunin kernel: device blocksize: 4096
>> Mar 22 13:47:33 bakunin kernel: grow_buffers: requested out-of-range
>> block 197478301302784 for device dm-14
>> Mar 22 13:47:33 bakunin kernel: EXT4-fs error (device dm-14):
>> ext4_xattr_delete_inode: inode 1022: block 197478301302784 read error
>
> That's another indication of data corruption in inode 1022.  This
> could be hardware induced corruption; or it could be a software
> induced error.  There's been one other user with a RAID that had
> reported a strange corruption near the beginning of the filesystem, in
> the inode table.  How big is your filesystem, exactly?

5,158,556 K.

> Can you send me the output of dumpe2fs of the filesystem in question?

Attached, as well as the itable image.

By the way, yesterday's fsck on another file system (/home) placed
almost 8,500 (!) files and directories in lost+found. I have not a
single error message regarding this device in my log files. All
files/directories were originally placed in the same parent directory.

    Richard

View attachment "dumpe2fs_dm-14_usr.txt" of type "text/plain" (81001 bytes)

Download attachment "itable_dm-14_usr.img" of type "application/octet-stream" (4096 bytes)