lvm-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Winston Wen <wentao@uniontech.com>
Cc: lvm-devel@lists.linux.dev
Subject: Re: lvm2-monitor.servcie block boot process due to bad storage device
Date: Thu, 25 Apr 2024 12:02:44 -0500	[thread overview]
Message-ID: <ZiqMtOozvoNW2h-f@redhat.com> (raw)
In-Reply-To: <BA135FC1810D838F+20240423084101.40b9659c@winn-pc>

On Tue, Apr 23, 2024 at 08:41:01AM +0800, Winston Wen wrote:
> Hi,
> 
> If a device's IO does not respond, it will block in the path of
> partition scanning. But at this point, it has already created the
> part0, like /dev/sda, in devtmpfs, but the mutex of the device has been
> held by the partition scanning code, so all processes attempting to
> open it will enter a wait.
> 
> lvm scans and opens block devices under /dev/ during startup, so if
> there are any bad devices mentioned above, lvm2-monitor.server will be
> blocked, and because its type is oneshot, it will block the boot
> process, even if the poor device is not using lvm.
> 
> May I ask if there is a way to avoid it? For example, can the
> type of this service be changed from oneshot to simple? Or is there
> any other better way?

I suggest using the devices file, or a filter (depending on your lvm
version) to prevent lvm from scanning devices other than PVs.

Dave


      parent reply	other threads:[~2024-04-25 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  0:41 lvm2-monitor.servcie block boot process due to bad storage device Winston Wen
2024-04-23 11:41 ` Zdenek Kabelac
2024-04-25 17:02 ` David Teigland [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=ZiqMtOozvoNW2h-f@redhat.com \
    --to=teigland@redhat.com \
    --cc=lvm-devel@lists.linux.dev \
    --cc=wentao@uniontech.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 read-only IMAP folder(s) and NNTP newsgroup(s).