From: Nate Carlson <natecars@natecarlson.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvcreate - race condition creating snapshots
Date: Sun, 11 Jun 2006 02:53:24 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0606110251220.864@tungsten.msp.technicality.org> (raw)
In-Reply-To: <448B01F9.604@solid-soft.at>
On Sat, 10 Jun 2006, Robert Valentan wrote:
> I think, there is a race condition in lvcreate while makeing a new
> snapshot.
>
> System: Tyan with 2 Opteron 246
> xen 3.0.2-3
> linux 2.6.16.13
> lvm 2.02.07
> 3ware-Raid 9550 Raid5
>
> Under xen i was unable to create a snapshot, I got always "LV
> system/snap in use: not deactivating". Without xen, i got occasionally a
> snapshot.
<..>
> i got always a snapshot (on all 3 systems!). I think, there is an other
> thread which is creating the new lv, and it will take longer as the
> lvcreate will "think". I have to less knowledge to make a patch, which
> is waiting for the correct event (creating lv complete).
Are you running udev, perchance?
Try reading the thread entitled "Problem creating snapshots with 2.6.16.9
and LVM 2.02.06", and refer to the following Debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343671
In the bug history, there's debate if it's a problem with LVM or udev,
although your mail seems to indicate LVM. :)
(Note that I've also been having this problem for awhile, and the udev
"hack" seems to resolve it..)
------------------------------------------------------------------------
| nate carlson | natecars@natecarlson.com | http://www.natecarlson.com |
| depriving some poor village of its idiot since 1981 |
------------------------------------------------------------------------
prev parent reply other threads:[~2006-06-11 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 17:31 [linux-lvm] lvcreate - race condition creating snapshots Robert Valentan
2006-06-11 7:53 ` Nate Carlson [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=Pine.LNX.4.63.0606110251220.864@tungsten.msp.technicality.org \
--to=natecars@natecarlson.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).