From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Peter Teoh <htmldeveloper@gmail.com>,
Theodore Tso <tytso@mit.edu>,
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: Tue, 22 Apr 2008 19:52:29 -0500 [thread overview]
Message-ID: <480E884D.7010602@redhat.com> (raw)
In-Reply-To: <20080422213144.GW2775@webber.adilger.int>
Andreas Dilger wrote:
> On Apr 22, 2008 12:02 -0500, Eric Sandeen wrote:
>> Peter Teoh wrote:
>>> On Sun, Apr 20, 2008 at 3:07 AM, Eric Sandeen <sandeen@redhat.com> wrote:
>>>> 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?)
>>> Can I know where is this script? Or if u cannot locate it, does it
>>> have any resemblance to all the stuff mentioned below?.
>> Google for "lvcheck" and find it buried in a thread "forced fsck
>> (again?)" on the ext3-users list - I'm not sure if it has an upstream
>> home anywhere yet...
>
> We thought the best place to put it would be in the lvm2 utilities, since
> it is tied to LVM snapshots (and not really a particular filesystem).
>
> Eric, any chance you could pass the script over to the LVM folks at RH?
> AFAIK, they are the official LVM/DM maintainers still (adopted as part of
> Sistina and GFS).
Sure, I'll see who I can bug :)
-Eric
next prev parent reply other threads:[~2008-04-23 0:54 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 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 8:01 ` Andi Kleen
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 [this message]
[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=480E884D.7010602@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=alexey.zaytsev@gmail.com \
--cc=htmldeveloper@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.