From: Andi Kleen <andi@firstfloor.org>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Andi Kleen <andi@firstfloor.org>,
Alexey Zaytsev <alexey.zaytsev@gmail.com>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Rik van Riel <riel@surriel.com>
Subject: Re: Mentor for a GSoC application wanted (Online ext2/3 filesystem checker)
Date: Mon, 21 Apr 2008 16:43:32 +0200 [thread overview]
Message-ID: <20080421144332.GA21028@one.firstfloor.org> (raw)
In-Reply-To: <20080421023342.GC9700@mit.edu>
> snaphot was taken. Even if it has been remounted read-only at this
> point, this gets really dicey. Consider that with certain types of
> corruption, if the filesystem continues to get modified, the
> corruption can get worse.
I see, but perhaps you could do that on at least some common
type of corruptions and only give up in the extreme cases?
Mind you I don't have a good feeling what common and uncommon
types are.
>
> > Or perhaps just tell the kernel which objects is suspicious and
> > should be EIOed.
>
> Yeah; you could do that, as long as it's not a guarantee that all of
> the objects which were suspicious were found. It would also be
Ok to do the 100% job you probably need metadata checksums and always
validate on initial read.
-Andi
next prev parent reply other threads:[~2008-04-21 14:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 14:20 Mentor for a GSoC application wanted (Online ext2/3 filesystem checker) Alexey Zaytsev
2008-04-19 1:29 ` Theodore Tso
2008-04-19 9:44 ` Alexey Zaytsev
2008-04-19 18:56 ` Theodore Tso
2008-04-19 19:07 ` Eric Sandeen
2008-04-19 22:04 ` Theodore Tso
2008-04-20 1:24 ` Eric Sandeen
2008-04-20 23:30 ` Andi Kleen
2008-04-20 23:42 ` Jamie Lokier
2008-04-21 8:01 ` Andi Kleen
2008-04-21 8:01 ` Andi Kleen
2008-04-21 11:51 ` Jamie Lokier
2008-04-21 17:29 ` Ricardo M. Correia
2008-04-21 17:40 ` Andi Kleen
2008-04-21 18:27 ` Ricardo M. Correia
2008-04-22 14:48 ` Jamie Lokier
2008-04-21 18:15 ` Ric Wheeler
2008-04-21 18:25 ` Eric Sandeen
2008-04-21 18:44 ` Ric Wheeler
2008-04-21 18:58 ` Matthew Wilcox
2008-04-21 19:11 ` Ric Wheeler
2008-04-21 0:27 ` Alexey Zaytsev
2008-04-21 9:45 ` Andi Kleen
2008-04-22 16:54 ` Peter Teoh
2008-04-22 17:02 ` Eric Sandeen
2008-04-22 23:37 ` Andreas Dilger
2008-04-23 0:52 ` Eric Sandeen
[not found] ` <480E4950.1090300@oracle.com>
[not found] ` <804dabb00804221633g1f61029dh7b27737134fc0b7a@mail.gmail.com>
[not found] ` <480E7954.9090408@oracle.com>
2008-04-23 1:02 ` Peter Teoh
2008-04-20 23:37 ` Andi Kleen
2008-04-21 2:33 ` Theodore Tso
2008-04-21 14:43 ` Andi Kleen [this message]
2008-04-21 0:23 ` Alexey Zaytsev
2008-04-21 12:53 ` Theodore Tso
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=20080421144332.GA21028@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=alexey.zaytsev@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=riel@surriel.com \
--cc=tytso@MIT.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 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.