linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Xen <list@xenhideout.nl>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm2 raid volumes
Date: Fri, 16 Sep 2016 17:03:18 +0200	[thread overview]
Message-ID: <2ea175a6dd1d81cb7137f2db8fee55d3@dds.nl> (raw)
In-Reply-To: <7308a436-1459-6097-3d02-239797867e8f@redhat.com>

Heinz Mauelshagen schreef op 16-09-2016 16:13:

> Yes, looks like you don't have the 2nd PV accessible by the time when
> the raid1 is being discovered and initially activated,
> hence the superblock can't be retrieved.
> 
> These messages seem to be coming from initramfs, so check which driver
> is missing/not loaded to access the 2nd PV.
> 
> The fact that you gain access to the raid1 completely after reboot (as
> you mention further down) tells the
> aforementioned fact is reasoning this degraded activation.
> I.e. disk driver loaded after root pivot.
> Please ensure it is available in the initramfs and loaded.
> 
> Heinz

Yes, thank you.

The problem was that the VG that contained the PV used as the 2nd PV was 
not getting activated at initramfs time.

I solved it now by creating some hooks that would obtain a hierarchical 
PV list from a running system and then ensure all PVs in that list that 
were also LVs, would get activated prior to the root device.

The issue is really that (on Ubuntu) LV activation is very selective in 
the initramfs. Of course it is an embedded or "enclosed" setup, maybe it 
is not recommended. Regardless the only issue was that LVs are getting 
selectively activated (only root and swap).

Regards.

      reply	other threads:[~2016-09-16 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 22:49 [linux-lvm] lvm2 raid volumes Steve Dainard
2016-08-03 13:10 ` Heinz Mauelshagen
2016-08-15 13:38   ` Xen
2016-09-16 14:13     ` Heinz Mauelshagen
2016-09-16 15:03       ` Xen [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=2ea175a6dd1d81cb7137f2db8fee55d3@dds.nl \
    --to=list@xenhideout.nl \
    --cc=linux-lvm@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).