Bug 839703 - Only RAID0 arrays can contain growable members.
Only RAID0 arrays can contain growable members.
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
17
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-12 11:19 EDT by Gerry Reno
Modified: 2012-07-12 13:33 EDT (History)
4 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Gerry Reno 2012-07-12 11:19:38 EDT
Description of problem:
While trying to create a RAID-1 array device from fixed sized RAID partitions received this error.
Only RAID0 arrays can contain grow able members.
Version-Release number of selected component (if applicable):


How reproducible:
Always.

Steps to Reproduce:
1. Install F17 from DVD.
2. Try to create RAID-1 array.
3.
  
Actual results:
See error.

Expected results:
Able to create RAID-1 array.

Additional info:
Comment 1 David Lehman 2012-07-12 12:40:54 EDT
I just did the following:

- Boot with two disks.
- Enter custom partitioning.
- Clear both disks completely.
- Create a RAID partition of fixed size 4000M on vda.
- Create a RAID partition of fixed size 4000M on vdb.
- Create a RAID1 array using the two aforementioned partitions
  with an ext4 fs mounted as the root fs.

It worked as expected.


Please attach the logs from your failed attempt:

 /tmp/anaconda.log
 /tmp/storage.log

Thanks.
Comment 2 Gerry Reno 2012-07-12 13:33:13 EDT
Just went back through and found that my spare partition was not set as fixed.

Once I changed it to fixed then the raid device got created. Sorry for the noise.

Closing bug.

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