Bug 1394640 - raid level 5 active with 1 out of 2 devices, algorithm 2
Summary: raid level 5 active with 1 out of 2 devices, algorithm 2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominik Perpeet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 06:20 UTC by lnie
Modified: 2016-11-17 05:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-17 05:54:52 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (33.05 KB, image/png)
2016-11-14 06:20 UTC, lnie
no flags Details
journal (147.77 KB, text/x-vhdl)
2016-11-14 06:21 UTC, lnie
no flags Details

Description lnie 2016-11-14 06:20:49 UTC
Created attachment 1220269 [details]
screenshot

Description of problem:

fresh install a VM,and add two disks using virt-manager,create a raid 5 disk using cockpit web,you will see the error in journal and on the screen of the server system after you  delete the raid.

raid level 4 is the same.

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

cockpit-123-1.fc25.x86_64.rpm

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2016-11-14 06:21:17 UTC
Created attachment 1220270 [details]
journal

Comment 2 Dominik Perpeet 2016-11-14 07:31:32 UTC
RAID 4 and 5 require three disks to actually work, so with only two disks they usually fall back to RAID 1, hence the warning.

What different behavior do you expect? Does using commandline storaged not throw a warning?

Comment 3 lnie 2016-11-17 05:54:52 UTC
Sorry for the wrong input.I saw this when I was trying to reproduce a raid 1 bug,and I'm going to close the bug now.Maybe it's better to warn users when 
they try to create raid 5, raid 4 with two disks,like cockpit dose now for raid 6.


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