Bug 112958 - Storage Modification Failure 6008 creating raid 5 with 3 logical partitions
Summary: Storage Modification Failure 6008 creating raid 5 with 3 logical partitions
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: i586 SUSE Other
: P5 - None : Normal
Target Milestone: RC 2
Assignee: Hannes Reinecke
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-25 12:47 UTC by Forgotten User vd_J2WSqeK
Modified: 2006-11-20 18:50 UTC (History)
1 user (show)

See Also:
Found By: System Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast logs (150.56 KB, application/x-gtar)
2005-08-25 12:47 UTC, Forgotten User vd_J2WSqeK 		Details
screenscrape of error (155.43 KB, image/jpeg)
2005-08-25 12:48 UTC, Forgotten User vd_J2WSqeK 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User vd_J2WSqeK 2005-08-25 12:47:06 UTC 
Code10 Beta 3

Single IDE HD system set up with 3 partitions: swap,  /,  data*
I started the Yast partitioner:
-deleted the data* partition.
-created 1 extended partition
-created 3 logical - 2G raid partitions
-started raid config
-added all 3 logical partitions to a raid 5 array
-finished
While creating the raid the attached error was received:
Storage modification failed  System errorcode was -6008
Failure occured during following action: Creating software RAID /dev/md0
Comment 1 Forgotten User vd_J2WSqeK 2005-08-25 12:47:36 UTC 
Created attachment 47536 [details]
yast logs
Comment 2 Forgotten User vd_J2WSqeK 2005-08-25 12:48:24 UTC 
Created attachment 47537 [details]
screenscrape of error
Comment 3 Thomas Fehr 2005-08-25 14:57:35 UTC 
This is because udev creates the devices asynchronously. 
mdadm is started, but the devices nodes for /dev/hda5, /dev/hda6 amd /dev/hda7
do not yet exist.

From y2log:
mdadm: Cannot open /dev/hda5: No such file or directory
mdadm: Cannot open /dev/hda6: No such file or directory
mdadm: Cannot open /dev/hda7: No such file or directory
mdadm: create aborted

There is a delay until the device nodes for the devices created by parted
show up in the system. Currently there is no way for YaST2 to know when this
is the case. 
We need a way to recognize if udev is finished with device node creation.

A workaround is to split partitioning and md creation. 
Create partitions in the first step, apply these changes,
Create md device yet.
Comment 4 Michael Gross 2005-08-25 15:23:07 UTC 
While trying to reproduce this bug, everything worked out until I wanted to
finalize the setup. Yast crashed with a Sig 11:

Segmentation fault at Storage.ycp:2083
/sbin/yast2: line 207:14252 Segmentation Fault [...]

If checked with fdisk that not even the partitioning was done after this, the
system was untouched (I wanted to delete one Partition and crate 3 logical
partitions to reproduce this bug).
Comment 5 Thomas Fehr 2005-08-25 15:31:26 UTC 
If you tried to create an extended partition and YaST2 crashed you probably hit
bug #112913. This bug will be fixed in beta#4.
You can avoid it of you create the extended partition with parted or fdisk. 
YaST2 in beta#3 only has problems creating the extended partition. If it exists 
it should be able to handle it fine.
Comment 6 Thomas Fehr 2005-09-08 15:22:15 UTC 
Should be fixed in RC2