linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: Ondrej Kozina <okozina@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] autoactivation fails
Date: Tue, 26 May 2015 14:05:34 +0200	[thread overview]
Message-ID: <20150526140534.4b04c406@leda.localdomain> (raw)
In-Reply-To: <55643397.7010609@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]

Ondrej Kozina <okozina@redhat.com> on Tue, 2015/05/26 10:49:
> On 05/26/2015 10:06 AM, Christian Hesse wrote:
> > Christian Hesse <list@eworm.de> on Mon, 2015/05/25 18:36:
> >
> > Actually running v2.02.220 with commit f8bf6410 on top. Volumes are
> > activated, but udev reports:
> >
> > timeout, giving up waiting for workers to finish
> >
> > This adds a boot delay of 30 seconds. Not perfectly sure if this is an
> > lvm2 issue though, chances are that this is caused by systemd v220
> > update. Any ideas?
>
> Could you try to boot with udev in debug mode? I'm not sure if it's same 
> as with Fedora distribution. It should be enough to put 'debug' keyword 
> among kernel parameters, though I'm not sure about Arch Linux distribution.
> 
> Paste udev debug messages here. Look for lines containing pvscan but the 
> reason for such timeout may be completely lvm2 unrelated.
> 
> Also I'm slightly confused here. Do we speak about system w/o systemd 
> involved at all? Or do Arch Linux boot to initramfs w/o systemd and 
> switch to systemd after root being actually mounted?
> 
> And on last question, do you ship upstream udev rules or do you install 
> Arch Linux specific rules?

First of all... It's not related to lvm2.
Even a system without lvm2 hook in initramfs is effected.

Looks like this is an upstream udev issue:
https://bugs.freedesktop.org/show_bug.cgi?id=90051

I will not bother you with any details of my system. ;)

Thanks a lot anyway!
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Chris           get my mail address:    */=0;b=c[a++];)
putchar(b-1/(/*               gcc -o sig sig.c && ./sig    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-05-26 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 12:19 [linux-lvm] autoactivation fails Christian Hesse
2015-05-21 15:09 ` Ondrej Kozina
2015-05-21 18:57   ` Christian Hesse
2015-05-21 19:50     ` Christian Hesse
2015-05-22  6:44     ` Ondrej Kozina
2015-05-25  7:16 ` Ondrej Kozina
2015-05-25 16:36   ` Christian Hesse
2015-05-26  8:06     ` Christian Hesse
2015-05-26  8:49       ` Ondrej Kozina
2015-05-26 12:05         ` Christian Hesse [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=20150526140534.4b04c406@leda.localdomain \
    --to=list@eworm.de \
    --cc=linux-lvm@redhat.com \
    --cc=okozina@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).