From: Martin Wilck <mwilck@suse.com>
To: "heming.zhao@suse.com" <heming.zhao@suse.com>,
David Teigland <teigland@redhat.com>
Cc: Peter Rajnoha <prajnoha@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM autoactivation and udev
Date: Thu, 24 Mar 2022 10:02:41 +0100 [thread overview]
Message-ID: <f0ef8a63b07a800d3346f6d4589b82fdfaa22957.camel@suse.com> (raw)
In-Reply-To: <9bacb637-77ce-5870-2f3c-9618ccceff81@suse.com>
On Thu, 2022-03-24 at 16:26 +0800, heming.zhao@suse.com wrote:
>
> Your concern is may right, "vgchange --monirtor y" will call
> lvmcache_label_scan() to search
> active VGs , meanwhile libudev hasn't done on some devs. And then
> vgchange will output
> some warning which can be ignored but may irritate users.
Again, I'm not so much concerned about the warning. More about what
happens if "vgchange --monitor y" ignores information from udev.
> In theory, if "vgchange --monitor y" only handles the VGs which
> created during initrd phase
> can avoid this problem.
Yes, but that's not how it currently behaves, right?
Martin
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-03-24 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:29 [linux-lvm] LVM autoactivation and udev Martin Wilck
2022-03-09 16:27 ` David Teigland
2022-03-09 17:04 ` Martin Wilck
2022-03-09 17:26 ` David Teigland
2022-03-09 19:48 ` Martin Wilck
[not found] ` <1f49866ba907896dc3678b47c5bb68d87e28b3c1.camel@suse.com>
2022-03-09 20:07 ` David Teigland
2022-03-09 17:07 ` Roger Heflin
2022-03-09 17:17 ` Martin Wilck
2022-03-21 8:57 ` heming.zhao
2022-03-21 16:44 ` David Teigland
2022-03-23 7:33 ` heming.zhao
2022-03-23 7:51 ` Martin Wilck
2022-03-24 8:26 ` heming.zhao
2022-03-24 9:02 ` Martin Wilck [this message]
2022-03-24 19:01 ` David Teigland
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=f0ef8a63b07a800d3346f6d4589b82fdfaa22957.camel@suse.com \
--to=mwilck@suse.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=prajnoha@redhat.com \
--cc=teigland@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).