From: Heming Zhao <heming.zhao@suse.com>
To: "linux-lvm@redhat.com" <linux-lvm@redhat.com>,
Martin Wilck <mwilck@suse.de>
Subject: [linux-lvm] system boot time regression when using lvm2-2.03.05
Date: Thu, 29 Aug 2019 13:52:48 +0000 [thread overview]
Message-ID: <c88b7c49-1046-ae78-4352-fa51e1ef7873@suse.com> (raw)
Hello List,
I found lvm2-2.03 has some performance regression when system booting.
My env as below:
```
x86-64 qemu vm, 2vcpu, 8G memory, 7 disks (per disk 1GB)
each disk have 128 primary partition, each partition size is 6MB.
total pvs: 896 (each partition create a pv), vgs 56 (every 16 pvs
create a vg), lvs 56 (each vg create a lv).
```
When using lvm2-2.02, it only took about a few seconds to enter login
prompt, but lvm2-2.03 took about 2mins.
## how to create lvm2-2.03.05
In fedora system,
go to website: https://src.fedoraproject.org/rpms/lvm2/tree/master
git clone https://src.fedoraproject.org/rpms/lvm2.git
To use rpmbuild to create rpm package and install.
And to run mkinitrd after changing the lvm.conf.
## teset result
below time got from the command: systemd-analyze --no-pager blame
the time line of "lvm2-pvscan@major:minor.service"
centos 7.6 (lvm2-2.02.180):
disable lvmetad: 2.341s
enable lvmetad: I wait about more than two hours, the system can't
enter login phase.
fedora-server (kernel: 5.2.9-200 with default installed lvm2:
lvm2-2.02.183-3)
use_lvmetad=0: 187ms
use_lvmetad=1: (no test)
fedora-server (kernel: 5.2.9-200 with rpmbuild: lvm2-2.03.05)
event_activation=1: 2min 3.661s
event_activation=0: 1min 57.478s
Could you give me some advice to locate this issue?
Thank you.
next reply other threads:[~2019-08-29 14:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 13:52 Heming Zhao [this message]
2019-08-29 14:37 ` [linux-lvm] system boot time regression when using lvm2-2.03.05 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
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=c88b7c49-1046-ae78-4352-fa51e1ef7873@suse.com \
--to=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=mwilck@suse.de \
/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.