From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Junfeng Yang <yjf@stanford.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net, mc@stanford.edu,
Madanlal S Musuvathi <madan@stanford.edu>,
"David L. Dill" <dill@cs.stanford.edu>
Subject: Re: [Ext2-devel] [CHECKER] warnings in fs/ext3/namei.c (2.4.19) where disk read errors get ignored, causing non-empty dir to be deleted
Date: Mon, 3 May 2004 16:10:01 +0200 [thread overview]
Message-ID: <20040503141001.GA23656@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20040427074455.GD30529@schnapps.adilger.int>
On Tue, 27 April 2004 01:44:55 -0600, Andreas Dilger wrote:
>
> Again a conscious decision. If a name is potentially inaccessible because
> of an IO error it is better to allow the creation of a potentially duplicate
> name than refuse creation of any new entries in the directory. It's a matter
> of allowing the filesystem to be used as well as possible in the face of
> failures vs. just giving up and refusing to do anything.
Do you mind if I doubt the sanity of whoever made that decision? When
my hard drive fails, I don't care about writing to the fs too much
anymore, I want to *notice* the failure early and to *read* as much as
possible, then put the drive on a pile for test hardware.
But then again, that's just me.
Jörn
--
A surrounded army must be given a way out.
-- Sun Tzu
next prev parent reply other threads:[~2004-05-03 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 6:41 Junfeng Yang
2004-04-27 7:44 ` [Ext2-devel] " Andreas Dilger
2004-05-03 9:59 ` Pavel Machek
2004-05-03 14:10 ` Jörn Engel [this message]
2004-05-03 16:16 ` Andreas Dilger
2004-05-03 17:33 ` Jörn Engel
2004-05-03 17:54 ` Andreas Dilger
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=20040503141001.GA23656@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dill@cs.stanford.edu \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=madan@stanford.edu \
--cc=mc@stanford.edu \
--cc=yjf@stanford.edu \
/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
all inboxes | Powered by JetHome®