Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 245277 - vgscan segmentation fault
vgscan segmentation fault
Product: Fedora
Classification: Fedora
Component: lvm2 (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Milan Broz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-21 22:47 EDT by srinivas varadaraj
Modified: 2013-02-28 23:05 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-19 13:59:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description srinivas varadaraj 2007-06-21 22:47:47 EDT
Description of problem:

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

How reproducible:

upgrade fc6 to fc7
update all packages with yum -y update
try mounting previously working lvm drives which are setup over software raids
md0 and md1
vgscan results in a crash. No logical volume is avaliable under /dev/<logical

however vgchange -a y shows the volume as enabled and lvm.static also detects
and shows the volume.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Alasdair Kergon 2007-07-01 22:59:38 EDT
This one got the wrong default assignments too.

What's supposed to happen for the QA contact now?  It only permits one email
address in that field!

Maybe some of the old QA contacts should be added to the initial cc lists as
part of fixing the merge breakage.

Another item for the post-implementation review.
Comment 2 Milan Broz 2007-07-02 03:59:02 EDT
Please could you provide system info - run lvmdump and attach created tar to
this bugzilla.

If not possible, please paste here output of "lvm version" and "dmsetup table"
commands, thanks.
Comment 3 Milan Broz 2007-07-19 13:59:34 EDT
I think this should be fixed in 2.02.27 lvm2 rpm, if not, please reopen this bug
and attach requested info, thanks.

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