Bug 136048 - lvm went kablooie
Summary: lvm went kablooie
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alasdair Kergon
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-10-17 06:05 UTC by Bill Nottingham
Modified: 2014-03-17 02:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-12-08 17:55:38 UTC
Type: ---
Embargoed:

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

Description Bill Nottingham 2004-10-17 06:05:02 UTC 
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 06:07:00 UTC 
Created attachment 105343 [details]
LVM. It's funtastic!
Comment 2 Bill Nottingham 2004-10-17 06:10:36 UTC 
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 06:17:57 UTC 
Preliminary guess is that it didn't like /dev/md14.
Comment 4 Jeremy Katz 2004-10-17 22:09:18 UTC 
This is ... suspicious.

  Volume group VolGroup00 metadata is inconsistent
  Volume group for uuid not found:
h2MpTBWmWmJqnw068Hx6BCesvGwXiIKVwlCd3BFpqgBXHdz3VN281cUyay6MYHiQ
  Failed to activate new LV.
ata.
    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 22:41:45 UTC 
2.00.27 will help fix this - may need anaconda changes or further lvm2
changes too
Comment 6 Sc 2004-11-26 05:54:21 UTC 
I too have this issue when trying to attach existing Sata raid drives.
Comment 7 Alasdair Kergon 2004-12-03 19:30:15 UTC 
Does 2.00.29 fix this?
Comment 8 Bill Nottingham 2004-12-03 20:54:44 UTC 
I don't have the filesystem in a state to reproduce this now. :/
Comment 9 Alasdair Kergon 2004-12-08 17:55:38 UTC 
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.