All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: 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: Sat, 19 Apr 2008 14:07:34 -0500	[thread overview]
Message-ID: <480A42F6.2030005@redhat.com> (raw)
In-Reply-To: <20080419185603.GA30449@mit.edu>

Theodore Tso wrote:
> On Sat, Apr 19, 2008 at 01:44:51PM +0400, Alexey Zaytsev wrote:
>> If it is a block containing a metadata object fsck has already read,
>> than we already know what kind of object it is (there must be a way
>> to quickly find all cached objects derived from a given block), and
>> can update the cached version. And if fsck has not yet read the
>> block, it can just be ignored, no matter what kind of data it
>> contains. If it contains metadata and fsck is intrested in it, it
>> will read it sooner or later anyway. If it contains file data, why
>> should fsck even care?

It seems to me that what the proposed project really does, in essence,
is a read-only check of a filesystem snapshot.  It's just that the
snapshot is proposed to be constructed in a complex and non-generic (and
maybe impossible) way.

If you really just want to verify a snapshot of the fs at a point in
time, surely there are simpler ways.  If the device is on lvm, there's
already a script floating around to do it in automated fasion.  (I'd
pondered the idea of introducing META_WRITE (to go with META_READ) and
maybe lvm could do a "metadata-only" snapshot to be lighter weight?)

-Eric

  reply	other threads:[~2008-04-19 19:09 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 [this message]
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
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=480A42F6.2030005@redhat.com \
    --to=sandeen@redhat.com \
    --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.