From: Alasdair G Kergon <agk@redhat.com>
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:56:45 +0100 [thread overview]
Message-ID: <20060609145645.GC7606@agk.surrey.redhat.com> (raw)
In-Reply-To: <20060609145135.6063312EDD@bluewhale.planbit.co.uk>
> > Wombat:~# lvcreate -L10G -n snapdisk -s /dev/clientstore/userdisk
> > LV clientstore/snapdisk in use: not deactivating
> > Couldn't deactivate new snapshot.
Could be interaction (not yet understood) with udev - try disabling udev while
running the command.
(Ref debian bug 343671)
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2006-06-09 14:56 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
2006-06-09 14:56 ` Alasdair G Kergon [this message]
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=20060609145645.GC7606@agk.surrey.redhat.com \
--to=agk@redhat.com \
--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).