All of lore.kernel.org
 help / color / mirror / Atom feed
From: suscricions@gmail.com
To: systemd-devel@lists.freedesktop.org
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [systemd-devel] Possible race condition with LVM activation during boot
Date: Thu, 7 Feb 2019 19:13:02 +0100	[thread overview]
Message-ID: <20190207191302.1b1dcadd@gmail.com> (raw)
In-Reply-To: <b2ccc7a2-b4fa-4acb-63d8-1126e7a01959@redhat.com>

El Thu, 7 Feb 2019 11:18:40 +0100
Peter Rajnoha <prajnoha@redhat.com> escribió:

> On 2/6/19 6:38 PM, suscricions@gmail.com wrote:
> > Hi,
> > 
> > First of all apologies if this is not the correct channel to request
> > for help with this issue. I've tried asking in Arch Linux forums
> > without luck for the moment.
> > 
> > Long story short, from time to time I'm dropped to a rescue shell
> > during boot because of a logical volume that cannot be found, so the
> > respective .mount service fails making the local-fs.target stop
> > normal boot process.
> > 
> > local-fs.target: Job local-fs.target/start failed with result
> > 'dependency'.
> > 
> > Under normal circumstances I'd assume that a logical volume should
> > be activated first in order to be mounted, but a few times mounting
> > happens first so causing the error. I think this can be a race
> > condition or something similar because strikes randomly. Booting
> > again avoids the problem for the moment, which happened twice
> > during past days.
> > 
> > All the relevant parts from logs and information about my system
> > partition scheme is posted here:
> > https://bbs.archlinux.org/viewtopic.php?pid=1830442
> > 
> > Hope some of you can help me to find the root cause and again
> > apologies if this is not the place or the issue is too obvious.
> >   
> 
> If there's a mount unit, it's bound to certain device for which
> systemd waits to appear on the system. So yes, the device must be
> activated first before the mounting happens. If device doesn't appear
> within a timeout, you usually get dropped to a rescue shell.
> 
> Please, if you hit the problem again, try to collect LVM debug info by
> running the "lvmdump -u -l -s" command that creates a tarball with
> various LVM-related debug info we can analyze. It contains content of
> the journal for the current boot, the udev environment, LVM
> configuration, device stack listing and various other useful
> information for more thorough debugging.
> 
> I'm adding CC linux-lvm, let's move this discussion there. Thanks.
> 

There's been a reply in Arch Linux forums and at least I can apply some
contingency measures. If it happens again I will provide more info
following your advice.

Many thanks!

--
Miguel

  reply	other threads:[~2019-02-07 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190206183841.69e38617@gmail.com>
2019-02-07 10:18 ` [linux-lvm] [systemd-devel] Possible race condition with LVM activation during boot Peter Rajnoha
2019-02-07 18:13   ` suscricions [this message]
2019-02-07 21:51     ` Martin Wilck
2019-02-08 13:12       ` suscricions

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=20190207191302.1b1dcadd@gmail.com \
    --to=suscricions@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=systemd-devel@lists.freedesktop.org \
    /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.