From: Christophe Saout <christophe@saout.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: LVM 2.6 compatibility?
Date: Wed, 07 Jan 2004 11:17:04 +0100 [thread overview]
Message-ID: <1073470624.18282.2.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <20040107090952.GO14285@lug-owl.de>
Am Mi, den 07.01.2004 schrieb Jan-Benedict Glaw um 10:09:
> Erm, not to mention that I've recently been hit by some bug. This is
> with LVM2 userland and LVM1 metadata. I just wanted to create a
> snapshot, but I got
Snapshots are not yet finished. There is experimental support in the
unstable device-mapper development tree. There's also experimental
support for pvmove there, and some new dm targets (multipath and crypt).
prev parent reply other threads:[~2004-01-07 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 13:59 LVM 2.6 compatibility? Roy Sigurd Karlsbakk
2004-01-06 15:31 ` Måns Rullgård
2004-01-07 8:41 ` venom
2004-01-07 9:09 ` Jan-Benedict Glaw
2004-01-07 10:17 ` Christophe Saout [this message]
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=1073470624.18282.2.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/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