All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Tsoy <alexander@tsoy.me>
To: lvm-devel@redhat.com
Subject: lvmetad activation problem with MD devices
Date: Tue, 1 Oct 2013 17:50:53 +0400	[thread overview]
Message-ID: <20131001175053.56abb90f@work.puleglot> (raw)
In-Reply-To: <524AB10B.2050705@redhat.com>

? Tue, 01 Oct 2013 13:24:59 +0200
Peter Rajnoha <prajnoha@redhat.com> ?????:

> On 10/01/2013 09:05 AM, Peter Rajnoha wrote:
> > On 09/30/2013 06:36 PM, Alexander Tsoy wrote:
> >> Commit 8d1d83504dcf9c86ad42d34d3bd0b201d7bab8f6 introduced the
> >> following problem. If MD device is assembled in initramfs and some LVs
> >> on it are not activated, then those LVs still not activated during
> >> system boot.
> > 
> > Yes, sorry for the problem. I'm just working on a fix. The source of
> > the problem here is that udev database is not handed over from initramfs
> > for MD devices and so the udev state is simply lost. The state information
> > we need is the MD activation state.
> 
> There's also a bug reported for this issue:
> 
>   https://bugzilla.redhat.com/show_bug.cgi?id=1011704
> 
> I've handed that over to dracut as we can solve this by adding a special
> 'OPTIONS+="db_persist"' udev rule to MD rules that are installed for MD
> devices in initramfs. This is already done for device-mapper devices in
> dracut.
> 
> The proposed patch is simple (also tested on my system where I reproduced
> the original problem):
> 
>   https://bugzilla.redhat.com/attachment.cgi?id=805841
> 
> Peter

Yeah, this looks like a proper fix.

Thanks for the detailed explanation.

-- 
Alexander Tsoy



      reply	other threads:[~2013-10-01 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 16:36 lvmetad activation problem with MD devices Alexander Tsoy
2013-09-30 18:18 ` Alexander Tsoy
2013-10-01  7:05 ` Peter Rajnoha
2013-10-01 11:24   ` Peter Rajnoha
2013-10-01 13:50     ` Alexander Tsoy [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=20131001175053.56abb90f@work.puleglot \
    --to=alexander@tsoy.me \
    --cc=lvm-devel@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 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.