From: Theodore Tso <tytso@mit.edu>
To: Richard <richard@r-selected.de>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Severe data corruption with ext4
Date: Mon, 23 Mar 2009 08:17:09 -0400 [thread overview]
Message-ID: <20090323121709.GD13368@mit.edu> (raw)
In-Reply-To: <b2080d80903230210w60d48530n9b98fdf71cf6fd18@mail.gmail.com>
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-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Tso <tytso@mit.edu>
To: Richard <richard@r-selected.de>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Severe data corruption with ext4
Date: Mon, 23 Mar 2009 08:17:09 -0400 [thread overview]
Message-ID: <20090323121709.GD13368@mit.edu> (raw)
In-Reply-To: <b2080d80903230210w60d48530n9b98fdf71cf6fd18@mail.gmail.com>
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
next prev parent reply other threads:[~2009-03-23 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 9:44 Severe data corruption with ext4 Richard
2009-03-20 10:01 ` Andrew Morton
2009-03-22 13:26 ` Richard
2009-03-23 2:05 ` Theodore Tso
2009-03-23 9:10 ` Richard
2009-03-23 12:17 ` Theodore Tso [this message]
2009-03-23 12:17 ` Theodore Tso
2009-03-23 14:20 ` Richard Höchenberger
2009-03-23 15:08 ` Theodore Tso
2009-03-23 15:08 ` Theodore Tso
2009-03-23 15:12 ` Richard Höchenberger
2009-03-26 18:05 ` Richard Höchenberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090323121709.GD13368@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@r-selected.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.