From: Phillip Susi <psusi@cfl.rr.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Steve Grubb <sgrubb@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] handle ext3 directory corruption better
Date: Tue, 31 Oct 2006 08:35:42 -0500 [thread overview]
Message-ID: <4547512E.8010603@cfl.rr.com> (raw)
In-Reply-To: <20061031095742.GA4241@ucw.cz>
Another expectation is that after the fsck, you won't loose any more
data that you could access by mounting the damaged filesystem. There
are a lot of horror stories out there of people only having a slightly
damaged fs, and after a fsck, they lost a lot more data.
Pavel Machek wrote:
>
> Nice... can you run the same tool against fsck, too?
>
> I did that some time ago, with less evil tool, and got some
> interesting results.
>
> (Expectation is that no matter how you corrupt fs, fsck will get it
> back to consistent state...)
> Pavel
next prev parent reply other threads:[~2006-10-31 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 15:29 [PATCH] handle ext3 directory corruption better Steve Grubb
2006-10-31 9:57 ` Pavel Machek
2006-10-31 13:35 ` Phillip Susi [this message]
2006-11-01 15:29 ` Steve Grubb
2006-11-10 20:57 ` Eric Sandeen
2006-11-12 13:39 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-10-20 19:17 Eric Sandeen
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=4547512E.8010603@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sgrubb@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox