All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	me@mooluv.com
Subject: Re: [linux-lvm] lvm Bug? - bad reaction to snapshot creation
Date: Tue, 10 Jun 2014 10:31:23 +0200	[thread overview]
Message-ID: <5396C25B.1060407@redhat.com> (raw)
In-Reply-To: <5395CA79.90508@mooluv.com>

Dne 9.6.2014 16:53, Leeman Strout napsal(a):
> On 06/09/2014 05:50 AM, Zdenek Kabelac wrote:
>> Dne 7.6.2014 01:26, Leeman Strout napsal(a):
>> 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?
> systemd 213-6 is what Arch reports, as far as I can tell from the PKGBUILD
> it's vanilla 213 plus 2 patches:
> - backport fix for faily MACAddress matching (FS#40675)
> - backport fix for fsck/udev mess (FS#40706)


this commit should be fixing problems for lvm2 & latest systemd:

e918a1b5a94f270186dca59156354acd2a596494

and this is systemd commit which has introduced problem:

3d06f4183470d42361303086ed9dedd29c0ffc1b

Unsure what do you have in your arch build.

>> 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 ?)
> After a clean restart of everything twice without doing snapshots, the initial
> lvcreate does not have the 'counter below zero' error.  And with special
> attention to make sure the snapshots are cleaned up prior to attempting a new
> snapshot I am not getting this initial decrement on lvcreate.

So could we consider this  'counter' case is solved ?

Zdenek

      parent reply	other threads:[~2014-06-10  8:31 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
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 [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=5396C25B.1060407@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.