From: Christian Hesse <mail@eworm.de>
To: Leeman Strout <me@mooluv.com>
Cc: LVM, development <linux-lvm@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] lvm Bug? - bad reaction to snapshot creation
Date: Wed, 11 Jun 2014 09:59:49 +0200 [thread overview]
Message-ID: <20140611095949.7c429a61@leda.localdomain> (raw)
In-Reply-To: <539722BD.20903@mooluv.com>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
Leeman Strout <me@mooluv.com> on Tue, 2014/06/10 11:22:
> On 06/10/2014 03:58 AM, Zdenek Kabelac wrote:
> > 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.
>
> This patch:
> http://lists.freedesktop.org/archives/systemd-devel/2014-June/019863.html
> applied and tested in Arch solves the issue.
This has been applied to systemd-213-9 (and systemd upstream) already. ;)
--
Schoene Gruesse
Chris
O< ascii ribbon campaign
stop html mail - www.asciiribbon.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-11 7:59 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 [this message]
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=20140611095949.7c429a61@leda.localdomain \
--to=mail@eworm.de \
--cc=linux-lvm@redhat.com \
--cc=me@mooluv.com \
--cc=zkabelac@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).