From: "Roger Lucas" <roger@planbit.co.uk>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: RE: [linux-lvm] Problem creating snapshots with 2.6.16.9 and LVM 2.02.06
Date: Fri, 9 Jun 2006 15:51:22 +0100 [thread overview]
Message-ID: <20060609145135.6063312EDD@bluewhale.planbit.co.uk> (raw)
In-Reply-To: <20060609134326.B1AAE12EDD@bluewhale.planbit.co.uk>
As a follow up, I have also tried it with the 2.6.16.20 kernel which is
fresh from kernel.org. Same problem.
> -----Original Message-----
> From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com]
> On Behalf Of Roger Lucas
> Sent: 09 June 2006 14:43
> To: 'LVM general discussion and development'
> Subject: [linux-lvm] Problem creating snapshots with 2.6.16.9 and LVM
> 2.02.06
>
> Hi,
>
> I am running what was Debian Sarge but has the new 2.6.16.9 kernel. I
> have
> made a few patches to the kernel (to add an Areca RAID driver and a few
> hardware sensors) but nothing in the device-mapper areas. I use the
> snapshots capability in LVM to snapshot the client's userdisk volume when
> backing it up.
>
> Until a couple days ago, I was running:
>
> Wombat:~# uname -a
> Linux Wombat 2.6.16.9.rwl7 #1 Tue May 16 20:25:14 BST 2006 i686 GNU/Linux
> Wombat:~# lvm version
> LVM version: 2.01.04 (2005-02-09)
> Library version: 1.01.00-ioctl (2005-01-17)
> Driver version: 4.4.0
> Wombat:~#
>
> and everything ran fine.
>
> A few days ago, I saw an e-mail from Alasdair on this mailing list saying
> that kernels 2.6.16 onwards should be using the later userspace tools.
> Following this, I downloaded and compiled the latest device mapper library
> (libdevmapper 1.02) and LVM tools (2.02.06). When I installed them on the
> machine and re-ran the backup script, I got an error from lvcreate when I
> tried to make the snapshot which I did not get before. I saw that Patrick
> Honing also reported this error on 29/5/06 on this mailing list, but
> couldn't see any reply.
>
> For me, this failure is 100% repeatable.
>
> Can anyone help shed light on this?
>
> If you need any more information then please let me know and I will send
> it
> in. My current option seems to be to drop back to the older 2.01.04 lvm
> and
> 1.01 dmapper but given Alasdair's mail, this seems to be risky.
>
> The full shell trace is below.
>
> Wombat:~# uname -a
> Linux Wombat 2.6.16.9.rwl7 #1 Tue May 16 20:25:14 BST 2006 i686 GNU/Linux
> Wombat:~# lvm version
> LVM version: 2.02.06 (2006-05-12)
> Library version: 1.02.07 (2006-05-11)
> Driver version: 4.5.0
> Wombat:~# lvs
> LV VG Attr LSize Origin Snap% Move Log Copy%
> backupimage clientstore -ri-ao 60.00G
> root clientstore -wi-ao 5.00G
> userdisk clientstore -wi-ao 60.00G
> Wombat:~# vgs
> VG #PV #LV #SN Attr VSize VFree
> clientstore 1 3 0 wz--n- 148.98G 23.98G
> Wombat:~# pvs
> PV VG Fmt Attr PSize PFree
> /dev/sda2 clientstore lvm2 a- 148.98G 23.98G
> Wombat:~# lvcreate -L10G -n snapdisk -s /dev/clientstore/userdisk
> LV clientstore/snapdisk in use: not deactivating
> Couldn't deactivate new snapshot.
> Wombat:~# lvs
> LV VG Attr LSize Origin Snap% Move Log Copy%
> backupimage clientstore -ri-ao 60.00G
> root clientstore -wi-ao 5.00G
> snapdisk clientstore -wi-a- 10.00G
> userdisk clientstore -wi-ao 60.00G
> Wombat:~#
>
>
> Many thanks in advance,
>
> Roger
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2006-06-09 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 13:43 [linux-lvm] Problem creating snapshots with 2.6.16.9 and LVM 2.02.06 Roger Lucas
2006-06-09 14:51 ` Roger Lucas [this message]
2006-06-09 14:56 ` Alasdair G Kergon
2006-06-09 18:51 ` [linux-lvm] Problem creating snapshots with 2.6.16.9 and LVM2.02.06 Roger Lucas
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=20060609145135.6063312EDD@bluewhale.planbit.co.uk \
--to=roger@planbit.co.uk \
--cc=linux-lvm@redhat.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).