From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] rc4 can't take snaphots of 0.9.1_beta7 lvs
Date: Tue, 9 Oct 2001 16:58:01 +0100 [thread overview]
Message-ID: <20011009165801.B851@btconnect.com> (raw)
In-Reply-To: <387040000.1002641567@tiny>; from mason@suse.com on Tue, Oct 09, 2001 at 11:32:47AM -0400
On Tue, Oct 09, 2001 at 11:32:47AM -0400, Chris Mason wrote:
>
> Hello everyone,
>
> Looks like the compatibility code in rc4 doesn't properly snapshot beta7
> logical volumes (2.4.10 kernel).
>
> To reproduce, I did this:
>
> Install 0.9.1 beta7 tools
>
> pvcreate /dev/sdb2
> vgcreate big /dev/sdb2
> lvcreate --size 6G -n lv1 big
> vgchange -a n
> rmmod lvm-mod
>
> Install rc4 tools
> vgscan
> vchange -a y
> mkfs /dev/big/lv1
> mount /dev/big/lv1 /data
> lvcreate --size 1G -n snap --snapshot /dev/big/lv1
> (trigger COW to snapshot)
>
> And I get these messages:
>
> lvm -- _pv_get_number failed for rdev = 0
> lvm -- giving up to snapshot /dev/big/lv1 on /dev/big/snap: couldn't
> prepare kiovec blocks (start probably isn't block aligned).
>
> Now that I can reliably reproduce on stock kernels/tools, I'm trying to
> trace it further. If anyone has ideas I'd love to hear them.
Some of the betas misaligned the logical volumes. If the volumes
aren't page aligned the snapshot code (which uses kiovecs) cannot
work. You have this problem. Fixing it isn't easy; you need to
shuffle your extents up or down by the appropriate amount. No one has
written a program to do this as of yet. Sorry.
- Joe
next prev parent reply other threads:[~2001-10-09 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 15:32 [linux-lvm] rc4 can't take snaphots of 0.9.1_beta7 lvs Chris Mason
2001-10-09 15:58 ` Joe Thornber [this message]
2001-10-09 16:30 ` Chris Mason
2001-10-09 19:30 ` Joe Thornber
2001-10-09 19:42 ` Joe Thornber
2001-10-09 20:01 ` Chris Mason
2001-10-09 19:48 ` Chris Mason
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=20011009165801.B851@btconnect.com \
--to=thornber@btconnect.com \
--cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).