From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com, me@mooluv.com
Subject: Re: [linux-lvm] lvm Bug? - bad reaction to snapshot creation
Date: Mon, 09 Jun 2014 11:50:00 +0200 [thread overview]
Message-ID: <53958348.3000501@redhat.com> (raw)
In-Reply-To: <53924E22.60403@mooluv.com>
Dne 7.6.2014 01:26, Leeman Strout napsal(a):
>
> Creating a snapshot throws an error "Attempted to decrement suspended device
> counter below zero." but succeeds. Removing the snapshot fails, attempting a
> 2nd time succeeds. Somewhere in this process the original LV gets locked and
> the system needs to be restarted to unlock it. As explained below this
> happens intermittently but regularly.
>
>
> Any additional info please let me know directly, I am not a subscriber,
Hi
Unsure if this relates to all your problem (since I'm not sure how arch linux
is in sync with udev rules & systemd version)
At certain moment systemd added a new 'feature' about locking devices while
updating internal udev state - this locking ignores any udev rule flags and
opens internal lvm2 devices - so while for now it's been again disabled for
'dm' devices - you might have installed version of system which has the 'lock
everything' feature in?
Thought this doesn't explain your 'counter below zero' error - this looks like
some incorrect udev rules are running in the field ?
(Or maybe multiple systemd-udevd are running ?)
Zdenek
next prev parent reply other threads:[~2014-06-09 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 23:26 [linux-lvm] lvm Bug? - bad reaction to snapshot creation Leeman Strout
2014-06-09 9:50 ` Zdenek Kabelac [this message]
2014-06-09 10:08 ` Marian Csontos
2014-06-09 14:55 ` Leeman Strout
2014-06-09 14:53 ` Leeman Strout
2014-06-10 7:58 ` Zdenek Kabelac
2014-06-10 13:45 ` Leeman Strout
2014-06-10 15:22 ` Leeman Strout
2014-06-11 7:59 ` Christian Hesse
2014-06-10 8:31 ` Zdenek Kabelac
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=53958348.3000501@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=me@mooluv.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).