Message-ID: <4547512E.8010603@cfl.rr.com>
Date: Tue, 31 Oct 2006 08:35:42 -0500
From: Phillip Susi <psusi@cfl.rr.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
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
References: <200610211129.23216.sgrubb@redhat.com> <20061031095742.GA4241@ucw.cz>
In-Reply-To: <20061031095742.GA4241@ucw.cz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 800
Lines: 21

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

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