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]

Message-ID: <20090323121709.GD13368@mit.edu>
Date:	Mon, 23 Mar 2009 08:17:09 -0400
From:	Theodore Tso <tytso@....edu>
To:	Richard <richard@...elected.de>
Cc:	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: Severe data corruption with ext4

On Mon, Mar 23, 2009 at 10:10:43AM +0100, Richard wrote:
> > 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.

OK, so about 5 gigs; not all that big at all.  I was starting to worry
that maybe we had some 32-bit signed/unsigned problem, but that would
be showing up in the 8+ TB range.

> Attached, as well as the itable image.

I've analyzed the itable image, and it looks valid; in particular, I
didn't see any evidence of corruption in inode 1022.

> 
> 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.

There is something very wrong going on here, and I'm at a loss why no
one else is reporting anything like what you are seeing.

Are you able to run a stock, unmodified mainline kernel on your
system?  At this point I'd really like to see if the problems you are
seeing can be replicated with a stock 2.6.29-rc8 kernel.

       	      		      	      - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/