Bug 1275377 - Anaconda is scanning disks for 12+ minutes, querying LVs again and again
Anaconda is scanning disks for 12+ minutes, querying LVs again and again
Product: Fedora
Classification: Fedora
Component: python-blivet (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vratislav Podzimek
Fedora Extras Quality Assurance
Depends On: 1327091
  Show dependency treegraph
Reported: 2015-10-26 13:34 EDT by Marian Csontos
Modified: 2016-12-20 10:10 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 10:10:13 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Tarball with logs (549.63 KB, application/x-gzip)
2015-10-26 13:34 EDT, Marian Csontos
no flags Details

  None (edit)
Description Marian Csontos 2015-10-26 13:34:03 EDT
Created attachment 1086562 [details]
Tarball with logs

Description of problem:
I have a VM with many disks (26x /dev/vdX), PVs (11), 2 VGs, 36 LVs, 145 LVs
including internal devices.

Installer seems to be stuck, program log looks like an infinite cycle.
After 12+ minutes is does finish scanning and after 5+ minutes of
intensive activating/deactivating devices it is ready to continue.

During the scanning anaconda spawned 8037 `lvm lvs --noheadings -o {pool_lv,data_lv,metadata_lv} ...` commands.
Only 423 unique ones, so it is running each unique command on average 19 times (the average is exactly 19, so it is not only on average but running each command 19 times.)
So it is running approximately 19x3 commands per each LV including internal ones.

Version-Release number of selected component (if applicable):

How reproducible:

Actual results:
Installer GUI is not responsive, program log looks like runing in circles.

Expected results:
Installer should not run for 17 minutes.

Additional info:
See attached tarball for disk layout and anaconda logs.

I wonder if something like `lvm lvs --noheading --nameprefixes --all -olv_name,pool_lv,data_lv,metadata_lv` would return results better suitable for machine consumption?

Perhaps running through something like this `https://gist.github.com/csonto/8baa94a22b8625a83931` to produce JSON.
Comment 1 Fedora End Of Life 2016-11-24 07:55:43 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Vratislav Podzimek 2016-11-30 02:43:05 EST
I believe this is no longer the case with LVM DBus and a few optimizations we did.
Comment 3 Fedora End Of Life 2016-12-20 10:10:13 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.