From: Martin Wilck <mwilck@suse.de>
To: LVM general discussion and development <linux-lvm@redhat.com>,
David Teigland <teigland@redhat.com>,
Heming Zhao <heming.zhao@suse.com>
Subject: Re: [linux-lvm] system boot time regression when using lvm2-2.03.05
Date: Fri, 06 Sep 2019 08:51:47 +0200 [thread overview]
Message-ID: <8b432efdabc3de82146ea6cb87b27c89556bf72e.camel@suse.de> (raw)
In-Reply-To: <b3790725-7a60-6fd7-ab64-8dfd75ce6628@suse.com>
On Fri, 2019-09-06 at 05:01 +0000, Heming Zhao wrote:
> I just tried to only apply below patch (didn't partly backout commit
> 25b58310e3).
> The attrs of lvs output still have 'a' bit.
>
> ```patch
> +#if 0
> if (!_online_pvscan_one(cmd, dev, NULL,
> complete_vgnames, saved_vgs, 0, &pvid_without_metadata))
> add_errors++;
> +#endif
IIUC this would mean that you skip David's "pvs_online" file generation
entirely. How did the auto-activation happen, then?
> ```
>
> the output of "systemd-analysis blame | head -n 10":
> ```
> 59.279s systemd-udev-settle.service
> 39.979s dracut-initqueue.service
> 1.676s lvm2-activation-net.service
Could it be that lvm2-activation-net.service activated the VGs? I can
imagine that that would be efficient, because when this service runs
late in the boot process, I'd expect all PVs to be online, so
everything can be activated in a single big swoop. Unfortunately, this
wouldn't work in general, as it would be too late for booting from LVM
volumes.
However I thought all lvm2-acticvation... services were gone with LVM
2.03?
Regards
Martin
next prev parent reply other threads:[~2019-09-06 6:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 13:52 [linux-lvm] system boot time regression when using lvm2-2.03.05 Heming Zhao
2019-08-29 14:37 ` David Teigland
2019-09-03 5:02 ` Heming Zhao
2019-09-03 15:17 ` David Teigland
2019-09-04 8:13 ` Heming Zhao
2019-09-05 12:35 ` Heming Zhao
2019-09-05 16:55 ` David Teigland
2019-09-06 4:31 ` Heming Zhao
2019-09-06 5:01 ` Heming Zhao
2019-09-06 6:51 ` Martin Wilck [this message]
2019-09-06 8:46 ` Heming Zhao
2019-09-06 14:15 ` David Teigland
2019-09-06 14:26 ` David Teigland
2019-09-06 14:03 ` David Teigland
2019-09-09 11:42 ` Heming Zhao
2019-09-09 14:09 ` David Teigland
2019-09-10 8:01 ` Martin Wilck
2019-09-10 15:20 ` David Teigland
2019-09-10 20:38 ` Zdenek Kabelac
2019-09-11 7:17 ` Martin Wilck
2019-09-11 9:13 ` Zdenek Kabelac
2019-09-12 13:58 ` Martin Wilck
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=8b432efdabc3de82146ea6cb87b27c89556bf72e.camel@suse.de \
--to=mwilck@suse.de \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@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 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.