linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ondrej Kozina <okozina@redhat.com>
To: list@eworm.de
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] autoactivation fails
Date: Thu, 21 May 2015 17:09:38 +0200	[thread overview]
Message-ID: <555DF532.7050904@redhat.com> (raw)
In-Reply-To: <20150521141955.70ebe714@leda.localdomain>

Hi Christian,

On 05/21/2015 02:19 PM, Christian Hesse wrote:
> Hello everybody,
>
> with recent lvm2 I had problems booting an Arch Linux system with non-systemd
> initramfs. lvmetad is launched, but volumes are not activated. A git bisect
> reported this bad commit:
> commit fe30658a4d5fe4e4e6bb346c9c9ee7142a98f49d
> Author: Ondrej Kozina <okozina@redhat.com>

I would like to ask you for more information about the issue. First, 
have you managed to collect any error messages during the init phase 
where it's supposed to fail?

The thing about that particular commit is it could possibly break 
background polling, but I don't see (yet) how it could have damaged the 
activation code. Have you tried to reboot a system where any operation 
like: pvmove, lvconvert --merge or lvconvert mirror conversion was in 
progress in background before you rebooted the system by any chance?

Second step would be to unmute the eventual background processes spawned 
during activation. To do it just uncomment

// #define DEBUG_CHILD

in tools/toollib.c:76 lvm2 sources and rebuild.

This should expose all error messages from within the forked off 
processes. Also, if you could perhaps give me some hints how to get the 
Arch Linux in the same state as when you experienced the issue it would 
help us as well.

Regards
Ondrej

  reply	other threads:[~2015-05-21 15:09 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 [this message]
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

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=555DF532.7050904@redhat.com \
    --to=okozina@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=list@eworm.de \
    /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).