From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: mauelshagen@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: LVM snapshotting broken?
Date: Fri, 27 Oct 2000 00:44:04 +0200 [thread overview]
Message-ID: <20001027004404.A1282@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.21.0010261632440.15696-100000@duckman.distro.conectiva> <Pine.LNX.4.21.0010261834360.15696-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0010261834360.15696-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, Oct 26, 2000 at 06:34:48PM -0200
On Thu, Oct 26, 2000 at 06:34:48PM -0200, Rik van Riel wrote:
> On Thu, 26 Oct 2000, Rik van Riel wrote:
>
> > it looks like the LVM snapshotting in 2.4 doesn't allow you
> > to create snapshots from anything else than the _first_ LV
> > in the VG...
>
> OK, I reproduced it in 2.2 as well ... ;(
Which 2.2.x? LVM isn't supported in 2.2.18pre17 or any other previous version.
For some irrelevant reason I always test snapshotting on a LV with minor
number > 1 and the kernel side definitely works with 2.2.18pre17aa1:
laser:/home/andrea # ls -l /dev/vg1/lv*
brw-r----- 1 root root 58, 0 Oct 27 2000 /dev/vg1/lv0
brw-r----- 1 root root 58, 1 Oct 27 2000 /dev/vg1/lv1
laser:/home/andrea # lvcreate -s -n lv1-snap /dev/vg1/lv1 -L 400M
lvcreate -- INFO: using default snapshot chunk size of 64 KB
lvcreate -- doing automatic backup of "vg1"
lvcreate -- logical volume "/dev/vg1/lv1-snap" successfully created
laser:/home/andrea # lvremove -f /dev/vg1/lv1-snap
lvremove -- doing automatic backup of volume group "vg1"
lvremove -- logical volume "/dev/vg1/lv1-snap" successfully removed
laser:/home/andrea #
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-26 22:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 18:36 LVM snapshotting broken? Rik van Riel
2000-10-26 20:34 ` Rik van Riel
2000-10-26 22:44 ` Andrea Arcangeli [this message]
2000-10-26 23:10 ` Marcelo Tosatti
2000-10-27 0:22 ` Andrea Arcangeli
2000-10-27 13:32 ` Rik van Riel
2000-10-27 13:44 ` Andrea Arcangeli
2000-10-27 13:55 ` Rik van Riel
2000-10-27 14:19 ` Andrea Arcangeli
2000-10-28 20:02 ` Heinz J. Mauelshagen
2000-10-28 22:07 ` Rik van Riel
2000-10-26 23:37 ` [linux-lvm] " Heinz J. Mauelshagen
2000-10-26 23:37 ` Heinz J. Mauelshagen
2000-10-26 23:53 ` [linux-lvm] " Christoph Hellwig
2000-10-26 23:53 ` Christoph Hellwig
2000-10-27 1:28 ` Christoph Hellwig
2000-10-27 1:28 ` Christoph Hellwig
2000-10-27 0:55 ` 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=20001027004404.A1282@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mauelshagen@sistina.com \
--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.