Bug 1477218

Summary: RAID support too restrictive / broken
Product: [Fedora] Fedora Reporter: Wolfgang Denk <wd>
Component: python-blivetAssignee: Blivet Maintenance Team <blivet-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: amulhern, anaconda-maint-list, blivet-maint-list, g.kaviyarasu, jkonecny, jonathan, mkolman, rvykydal, sbueno, vanmeeuwen+fedora, vponcova, vtrefny, wd
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 18:20:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Tarball with installation log files none

Description Wolfgang Denk 2017-08-01 13:41:46 UTC
Description of problem:

I run a system with 2 disks.  Fr reasons of reliability I want mirroring, for reasons of (single-thread) performance I want to use RAID10 for this - see [1]
for details.

[1] https://blog.a2o.si/2014/09/07/linux-software-raid-why-you-should-always-use-raid-10-instead-of-raid-1/

Problem 1: The installer does not allow to create such a RAID configuration; I did not even find a way to provide options like "--layout=f2", but creating a RAID10 from only 2 disks seems to be totally impossible.

Problem 2: So I pre-formatted the disks in another machine, created all needed partitions and RAID arrays.  I can see that the installer recognizes and starts the arrays, so this looks fine.  BUT:

- Booting Fedora-Server-dvd-x86_64-26-1.5.iso, the installer hangs before starting the GUI; the mouse pointer appears, then the GUI hangs forever.

- Booting Fedora-Workstation-Live-x86_64-26-1.5.iso, I can start the installer.  But when I try to select the artitions needed for the arrays, it will complain that I need at least 4 drives for a RAID10 array.  Which is incorrect.

So there is no way to use standard installation for such a configuration!

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


How reproducible:

always.

Steps to Reproduce:

see above.

Actual results:

Installer does not support needed configuration

Expected results:


Installer allows the user to set up system as needed.

Additional info:

Comment 1 Jiri Konecny 2017-08-02 07:38:57 UTC
Hello,

As I see this you are experiencing two issues here.

First, we are not supporting raid 10 on only two devices.
This is correct, we are using blivet library for partitioning which does not support this scheme. We need to reassign this issue to the python-blivet.

Second, the pre-formatted partitioning can't be used inside of Anaconda. This should be working and it could be a bug inside of Anaconda.

For both of these issues to be solved the logs from the failed installation would be really valuable. You can obtain these logs by switching tty (Ctrl+Alt+F1 for tmux instance or Ctrl+Alt+F2 for normal console) and grabbing logs from /tmp/*.log then upload these logs here.

Thank you for reporting this issue.

Comment 2 Wolfgang Denk 2017-11-09 20:05:45 UTC
Created attachment 1350094 [details]
Tarball with installation log files

Tarball with installation log files - running from Fedora-Workstation-Live-x86_64-27_Beta-1.5.iso

Comment 3 Wolfgang Denk 2017-11-09 20:06:37 UTC
Same problems with beta of Fedora 27 when trying the installation from the Fedora-Workstation-Live-x86_64-27_Beta-1.5.iso disk.

Comment 4 Jiri Konecny 2017-11-10 07:04:10 UTC
Hi Wolfgang,

I have a good news. We have new storage option in the text UI and the kickstart installation from F27. You can now use mountpoint assignment solution which works in a way -- create your partitioning and just attach mountpoints. This should fix your second problem.

For the first problem I'm switching this bug to the storage library.

Thank you for the logs.

Comment 5 Wolfgang Denk 2017-11-17 07:35:02 UTC
How exactly would I use this?
The live installer (Fedora-Workstation-Live ISO) does not seem to offer anything like that - or I'm missing it.
Where can I find documentation for this?

Comment 6 Jiri Konecny 2017-11-20 09:06:30 UTC
Hello Wolfgang,

Yes, you are right. You don't have this option on live installation this is useful for automatic kickstart installation and TUI installations. In GUI Live installation you basically don't need this at all. You can use tools like blivet-gui, gparted or shell to create your partitioning and after that run Anaconda. Of course first the installer hang problem needs to be fixed.

Jirka

Comment 7 Ben Cotton 2018-11-27 18:08:07 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2018-11-30 18:20:57 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.