archive mirror
 help / color / mirror / Atom feed
From: Xen <>
Subject: [linux-lvm] pvscan hung in LVM 160
Date: Tue, 23 Jan 2018 18:34:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.LRH.2.21.1801231822270.25@localhost> (raw)

I have a small question if I may ask.

I upgraded one of my systems to LVM 160, I know that's still rather old.

During boot, pvscan hangs, I don't know if this is because udev is 

The pvscan --background never completes.

If I remove --background, pvscan instantly exits with code 3.

Consequently, none of my volumes are activated save what comes down to the 
root device, because it is activated explicitly, this is Ubuntu Xenial 

The thing only started happening when I upgraded LVM to a newer version.

Though pvscan exits with 3, at least my system doesn't take 6 minutes to 
boot now.

My only question is: was this a known bug in 160 and has this since been 
fixed, and if so, in what version?

Some people on Arch investigated this bug when 160 was current (around 
2014) and for them the bug was caused by udev exiting before pvscan could 

The basic boot delays are caused by udevadm settle calls.


                 reply	other threads:[~2018-01-23 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.21.1801231822270.25@localhost \ \ \

* 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).