Bug 88407 - kickstart won't install swap on mirror md
kickstart won't install swap on mirror md
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-04-09 17:49 EDT by jmccann
Modified: 2015-01-14 18:19 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-11 13:03:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kickstart configuration used (2.69 KB, text/plain)
2003-04-09 17:51 EDT, jmccann
no flags Details

  None (edit)
Description jmccann 2003-04-09 17:49:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401

Description of problem:
It seems that kickstart won't install swap on a RAID1 metadevice.

The installer says something like "need two devices for mirror" and then reboots.

I got this error message with 8.0 too but it continued with the install.

A fault tolerant system should have swap on a mirror.

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

How reproducible:

Steps to Reproduce:
1. install swap on a RAID1 device during KS

Actual Results:  reboots

Expected Results:  Works.

Additional info:
Comment 1 jmccann 2003-04-09 17:51:20 EDT
Created attachment 91049 [details]
Kickstart configuration used

Sensitive information has been removed fron ks.cfg.
Comment 2 Michael Fulbright 2003-04-11 13:03:15 EDT
You need to specify a mount point of 'swap', ie:

  raid --level=1 --device=md0 --fstype swap raid.01 raid.02

should be:

  raid swap --level=1 --device=md0 --fstype swap raid.01 raid.02

I'll add some sanity checking for the mount point when we parse the ks.cfg.
Comment 3 jmccann 2003-04-11 13:22:03 EDT
Sorry to comment on a closed bug.  Thanks for the fix!  However, the ks.cfg file
came directly from redhat-config-kickstart.  So, maybe that has a bug?

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