Bug 19310

Summary:	Can't create raid devices/filesystems
Product:	[Retired] Red Hat Linux	Reporter:	Alexandre Oliva <aoliva>
Component:	anaconda	Assignee:	Michael Fulbright <msf>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-11-13 20:53:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexandre Oliva 2000-10-18 09:27:31 UTC

After creating two 1-Gb raid partitions in disks sda and sdb (one in each),
I chose to create a Linux filesystem out of them, to be mounted in `/l',
and named the device /dev/raid/l (I've also tried /dev/raid-l, without
success).  (Actually, I have created more than one partition in one of the
disks, in one of my attempts, but I *think* I've also tried 1 parition per
disk before giving up and setting up raid by hand after a regular
installation).

All was fine until the installation got to the point of creating the actual
filesystems, just before packages start to be installed: I got an exception
from the Python interpreter, and the installation was aborted.

Please let me know if you need further information to duplicate the problem.

Comment 1 Brock Organ 2000-10-18 19:28:13 UTC

could you attach the text of the anaconda exception to this report ...? that
would be helpful ... :)

Comment 2 Alexandre Oliva 2000-10-25 02:32:13 UTC

That would be hard.  I have already managed to create some raid devices, and I'd
rather not mess up with them.  Since I don't have any free disk space, and the
problem shows up quite late in the installation process, I fear changes in the
partition table may make it to disk before the failure, destroying the data I
already have.  Sorry, I should have noted the error message when I first got it,
but I thought it would have been easy to duplicate, since I could do it so many
times :-)

Comment 3 Michael Fulbright 2000-11-13 20:53:27 UTC

If you ever have a problem like this again please reopen this bug. We have not
seen this behaviour in our testing so perhaps it was something specific to your
setup.