From: Xose Vazquez Perez <xose@wanadoo.es>
To: linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
mauelshagen@sistina.com, marcelo.tosatti@cyclades.com,
hch@infradead.org
Subject: Re: [PATCH] 2.4.25--pre4 VFS lvm_snapshots
Date: Mon, 02 Feb 2004 03:44:55 +0100 [thread overview]
Message-ID: <401DB9A7.4030104@wanadoo.es> (raw)
Christoph Hellwig wrote:
> The patch still doesn't get better by that. And even if it was this
> would clearly be a feature for 2.6, not 2.4.
Without this patch there is no warranty that a LVM_snapshot is updated
like the FS that is trying to replicate. DANGER !!!
I only see one solution:
to stop FS IO, and then # sync; sync; sync; lvcreate -s ...
Maybe it's needed to write, in the code or a doc, some warning about this
or to put a pointer to this patch :-?
--
Software is like sex, it's better when it's bug free.
next reply other threads:[~2004-02-02 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 2:44 Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-07 15:51 [PATCH] 2.4.25--pre4 VFS lvm_snapshots Xose Vazquez Perez
2004-01-07 16:12 ` Christoph Hellwig
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=401DB9A7.4030104@wanadoo.es \
--to=xose@wanadoo.es \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=mauelshagen@sistina.com \
/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