Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 136048 - lvm went kablooie
lvm went kablooie
Product: Fedora
Classification: Fedora
Component: lvm2 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alasdair Kergon
Depends On:
Blocks: FC3Target FC4Target
  Show dependency treegraph
Reported: 2004-10-17 02:05 EDT by Bill Nottingham
Modified: 2014-03-16 22:49 EDT (History)
4 users (show)

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

Attachments (Terms of Use)
LVM. It's funtastic! (675.08 KB, text/plain)
2004-10-17 02:06 EDT, Bill Nottingham
no flags Details
more breakage (49.51 KB, text/plain)
2004-10-17 02:10 EDT, Bill Nottingham
no flags Details

  None (edit)
Description Bill Nottingham 2004-10-17 02:05:02 EDT
As an aside, we should probably work on ways to get these dumps
somewhere other than craptastic floppy drives.
Comment 1 Bill Nottingham 2004-10-17 02:07:00 EDT
Created attachment 105343 [details]
LVM. It's funtastic!
Comment 2 Bill Nottingham 2004-10-17 02:10:36 EDT
Created attachment 105344 [details]
more breakage

This is what happened when I just tried to reboot anaconda on the same box
after it crashed. Worked around by nuking the disk, of course. :/
Comment 3 Bill Nottingham 2004-10-17 02:17:57 EDT
Preliminary guess is that it didn't like /dev/md14.
Comment 4 Jeremy Katz 2004-10-17 18:09:18 EDT
This is ... suspicious.

  Volume group VolGroup00 metadata is inconsistent
  Volume group for uuid not found:
  Failed to activate new LV.
    Creating volume group backup "/etc/lvm/backup/VolGroup00"
  Volume group "VolGroup00" successfully created
l volumes for volume group VolGroup00.
  format_text: _vg_read failed to read VG VolGroup00
    Set up physical volume for "/dev/md0" with 163829376 available sectors
  Physical volume "/dev/md0" successfully created
Comment 5 Alasdair Kergon 2004-11-24 17:41:45 EST
2.00.27 will help fix this - may need anaconda changes or further lvm2
changes too
Comment 6 Sc 2004-11-26 00:54:21 EST
I too have this issue when trying to attach existing Sata raid drives.
Comment 7 Alasdair Kergon 2004-12-03 14:30:15 EST
Does 2.00.29 fix this?
Comment 8 Bill Nottingham 2004-12-03 15:54:44 EST
I don't have the filesystem in a state to reproduce this now. :/
Comment 9 Alasdair Kergon 2004-12-08 12:55:38 EST
I'll assume the md-recognition code in 2.00.29 probably fixed it and
close this.

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