Bug 427114 - parted does not allow RAID or LVM types in BSD partitioned disks
parted does not allow RAID or LVM types in BSD partitioned disks
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: parted (Show other bugs)
8
alpha Linux
low Severity low
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-31 17:58 EST by Jay Estabrook
Modified: 2008-02-05 20:17 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-05 20:17:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
allow RAID or LVM type partitions on BSD partitioned disk (2.65 KB, patch)
2007-12-31 17:58 EST, Jay Estabrook
no flags Details | Diff

  None (edit)
Description Jay Estabrook 2007-12-31 17:58:19 EST
Description of problem:

On Alpha, SRM console requires BSD stype partitions for booting. The current
parted code does not allow RAID or LVM types of partitions to be created on
BSD-partitioned disks.


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

parted-1.8.6-12.fc8


How reproducible:

Every time.


Steps to Reproduce:
1. install F8 to Alpha
2. allow the autopartitioner to attempt making an LVM partition on BSD disk
3.
  
Actual results:

Error exit.


Expected results:

Correct RAID or LVM partition on BSD disk.


Additional info:

Attached is a patch to fix the problem.
Comment 1 Jay Estabrook 2007-12-31 17:58:19 EST
Created attachment 290596 [details]
allow RAID or LVM type partitions on BSD partitioned disk
Comment 2 David Cantrell 2008-02-05 19:35:43 EST
Thanks for the patch.  Fixing it in rawhide and releasing an update for F-8.
Comment 3 David Cantrell 2008-02-05 20:17:38 EST
Actually, just going to fix it in rawhide as we don't do an Alpha build of Fedora.

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