From: Theodore Tso <tytso@mit.edu>
To: Heikki Orsila <shdl@zakalwe.fi>
Cc: Chris Holvenstot <cholvenstot@comcast.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Major SATA / EXT3 Issue?
Date: Wed, 31 Oct 2007 03:25:54 -0400 [thread overview]
Message-ID: <20071031072554.GC20965@thunk.org> (raw)
In-Reply-To: <20071030135923.GA3441@zakalwe.fi>
On Tue, Oct 30, 2007 at 03:59:24PM +0200, Heikki Orsila wrote:
> 3. fsck -p on boot failed
>
> (it is very probable not many files were corrupted at this stage)
Maybe...
>
> 4. I ran fsck.ext3 -y
>
> => that corrupted lots and lots of files. This went
> into a loop, the fsck.ext3 restarted checking over and over again.
It's possible that e2fsck corrupted the files, but they also could
have been corrupted earlier by the earlier I/O errors. There are some
relatively rare filesystem corruptions which e2fsck doesn't handle as
gracefully as it should, though, I will admit. I would need to see
the e2fsck transcript to be sure.
Were there any messages about needing to relocate inode tables by any
chance?
- Ted
next prev parent reply other threads:[~2007-10-31 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 2:21 Major SATA / EXT3 Issue? Chris Holvenstot
2007-10-27 12:47 ` Alan Cox
2007-10-31 10:08 ` Chris Holvenstot
2007-10-27 14:14 ` Clemens Koller
2007-10-30 13:59 ` Heikki Orsila
2007-10-31 7:25 ` Theodore Tso [this message]
2007-10-31 9:24 ` Heikki Orsila
[not found] <fa.g6cnSE4eZYP/DJbEoDA1gYUnPfo@ifi.uio.no>
2007-10-28 18:37 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 0:30 Norbert Preining
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=20071031072554.GC20965@thunk.org \
--to=tytso@mit.edu \
--cc=cholvenstot@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shdl@zakalwe.fi \
/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.