From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH/RFC] - make ext3 more robust in the face of filesystem corruption
Date: Thu, 19 Oct 2006 11:04:11 -0500 [thread overview]
Message-ID: <4537A1FB.6030601@redhat.com> (raw)
In-Reply-To: <20061018222449.GK3509@schatzie.adilger.int>
Andreas Dilger wrote:
> On Oct 18, 2006 16:56 -0500, Eric Sandeen wrote:
>> Andreas Dilger wrote:
>>> The directory leaf data is kept in
>>> the page cache and there is a helper function ext2_check_page() to mark
>>> the page "checked". That means the page only needs to be checked once
>>> after being read from disk, instead of each time through readdir.
>> ah, sure. Hm... well, this might be a bit of a performance hit if it's
>> checking cached data... let me think on that.
>
> Well, having something like "ext3_dir_bread()" that verifies the leaf block
> once if (!uptodate()) would be almost the same as ext2 with fairly little
> effort. It would help performance in several places, at the slight risk
> of not handling in-memory corruption after the block is read...
How about just tweaking the existing ext3_bread so that it lets the
caller know whether or not it found an uptodate buffer? Seems
conceivable that more than just the dir code might want to do a data
sanity check, based on if this is a fresh read or not.
Could maybe even change the *err argument to a *retval; negative on
errors, else 0 == not read (found uptodate), 1 == fresh read (not found
uptodate). Or is that too much overloading...
-Eric
next prev parent reply other threads:[~2006-10-19 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 21:11 [PATCH/RFC] - make ext3 more robust in the face of filesystem corruption Eric Sandeen
2006-10-18 21:40 ` Andreas Dilger
2006-10-18 21:56 ` Eric Sandeen
2006-10-18 22:24 ` Andreas Dilger
2006-10-19 0:26 ` Eric Sandeen
2006-10-19 7:35 ` Andreas Dilger
2006-10-19 16:04 ` Eric Sandeen [this message]
2006-10-19 22:43 ` Eric Sandeen
2006-10-20 3:50 ` Andreas Dilger
2006-10-20 4:00 ` 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=4537A1FB.6030601@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
/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