From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
"Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-lvm@msede.com, marcelo@conectiva.com.br
Subject: Re: [linux-lvm] Re: LVM 2.2 snapshot bug
Date: Wed, 8 Nov 2000 11:11:29 +0000 [thread overview]
Message-ID: <20001108111129.G11411@redhat.com> (raw)
In-Reply-To: <200011072036.eA7Ka6s03317@webber.adilger.net>; from adilger@turbolinux.com on Tue, Nov 07, 2000 at 01:36:06PM -0700
Hi,
On Tue, Nov 07, 2000 at 01:36:06PM -0700, Andreas Dilger wrote:
> Andreas writes:
> It would probably be a lot better to simply change ext3 to handle the
> "proper snapshot" stuff that is in ReiserFS, so that at the time of the
> snapshot, the journal is flushed and the RECOVER flag is removed from
> the superblock (and returned afterwards).
Right --- that's easy to do, but it doesn't mean that it's OK to lie
about the ro_bits!
Cheers,
Stephen
next prev parent reply other threads:[~2000-11-08 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 10:55 [linux-lvm] LVM 2.2 snapshot bug Rik van Riel
2000-11-07 12:16 ` Heinz J. Mauelshagen
2000-11-07 14:42 ` Rik van Riel
2000-11-07 13:21 ` [linux-lvm] " Andrea Arcangeli
2000-11-07 14:56 ` Rik van Riel
2000-11-07 16:45 ` Andrea Arcangeli
2000-11-07 17:04 ` Stephen C. Tweedie
2000-11-07 19:51 ` Andrea Arcangeli
2000-11-07 20:36 ` Andreas Dilger
2000-11-08 11:11 ` Stephen C. Tweedie [this message]
2000-11-08 16:16 ` Andrea Arcangeli
2000-11-08 19:08 ` Andreas Dilger
2000-11-08 11:10 ` Stephen C. Tweedie
2000-11-08 16:53 ` Andrea Arcangeli
2000-11-07 23:04 ` Rik van Riel
2000-11-08 7:55 ` Heinz Mauelshagen
2000-11-08 13:44 ` Rik van Riel
2000-11-08 16:31 ` Andrea Arcangeli
[not found] ` <898720000.973701988@coffee>
2000-11-08 17:04 ` Andrea Arcangeli
2000-11-08 19:11 ` 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=20001108111129.G11411@redhat.com \
--to=sct@redhat.com \
--cc=adilger@turbolinux.com \
--cc=andrea@suse.de \
--cc=linux-lvm@msede.com \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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.