Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 439659 - Unable to install F9 Beta with existing LVM setup
Summary: Unable to install F9 Beta with existing LVM setup
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
 
Reported: 2008-03-30 01:26 UTC by e
Modified: 2008-04-21 15:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-21 15:28:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
anaconda.log (deleted)
2008-03-31 12:39 UTC, e 		no flags Details
lvmout (deleted)
2008-03-31 12:40 UTC, e 		no flags Details
/tmp/syslog (deleted)
2008-03-31 12:41 UTC, e 		no flags Details
vg metadata (deleted)
2008-03-31 12:48 UTC, e 		no flags Details
View All

Description e 2008-03-30 01:26:16 UTC 
Description of problem:

My workstation has 3 disc setup:

 /dev/md0 /dev/sd{a,b,c}1 RAID 1 -> ext3 (/boot)
 /dev/md1 /dev/sd{a,b,c}2 RAID 5 -> PV -> VG -> LV ext3 ubuntu (/)
                                             -> LV ext3 fedora (/)
                                             -> LV LUKS data

I attempted to install F9 Beta onto the LV "fedora". Anaconda would not
allow this.

I then attempted to create a new LV in the VG (the VG has ~ 50 G unallocated).
Annaconda would not allow this either.

Version-Release number of selected component (if applicable):
9 Beta x86-64

How reproducible:
100%

Steps to Reproduce:
1. Produce disc setup above
2. Boot F9 beta install media
3. Try to either view/edit existing LV or create a new LV
  
Actual results:

Error dialog of:

 "Not enough physical volumes

At least one unused physical volume
partition is needed to create an LVM
volume group"

Expected results:

For it to work.

Additional info:

Whilst Anaconda was able to display the volume group and logical volumes,
the physical volume /dev/md1 was marked with a type of "foreign".

Clicking delete on /dev/md1 gives an error of:

   "Unable to delete

This partition is part of the LVM volume group 'NAME_OF_MY_VOLUME_GROUP'

Anaconda did let me delete the LV "fedora", but I was unable to edit/create
LVs otherwise.
Comment 1 Jeremy Katz 2008-03-30 16:40:04 UTC 
Can you grab the /tmp/anaconda.log and /tmp/lvmout from this attempt?
Comment 2 e 2008-03-31 12:39:35 UTC 
Created attachment 299717 [details]
anaconda.log
Comment 3 e 2008-03-31 12:40:43 UTC 
Created attachment 299718 [details]
lvmout

File gets zeroed out on custom partitioning screen. Output here after clicking
back to choose partition layout.
Comment 4 e 2008-03-31 12:41:18 UTC 
Created attachment 299719 [details]
/tmp/syslog
Comment 5 e 2008-03-31 12:48:12 UTC 
Created attachment 299721 [details]
vg metadata

Produced by vgcfgbackup
Comment 6 e 2008-03-31 12:48:39 UTC 
Information attached
Comment 7 Jeremy Katz 2008-04-17 06:44:32 UTC 
I think that this should be fixed in the preview release which should be out in
the next day or so.  Can you try again with it?
Comment 8 e 2008-04-21 15:28:50 UTC 
Confirmed that bug is fixed with preview release.

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