Bug 222471

Summary: udev links wrong on DM Raid 1
Product: [openSUSE] openSUSE 10.2 Reporter: Stefan Fent <stefan.fent>
Component: BasesystemAssignee: Kay Sievers <kasievers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Blocker    
Priority: P5 - None CC: aosthof, jplack
Version: Beta 2 plus   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Stefan Fent 2006-11-18 08:52:50 UTC 
After creating a fakeRAID with 2 mirrored disks last last disk gets the EDD id 80,
which has to be the devicemapper device.
Guess: As the mbr signature is stored on both disks, the las disk wins, as its the last that is read.
This way we can't reliably check which device has to be used as boot device.
Comment 1 Kay Sievers 2006-11-18 11:47:23 UTC 
What does:
  /lib/udev/vol_id --export <device>
print for the raid-members?
Comment 2 Stefan Fent 2006-11-20 08:40:13 UTC 
Alex, please test
Comment 3 Alexander Osthof 2006-11-20 09:55:30 UTC 
Ok, here's the output to comment #1:

/lib/udev/vol_id --export /dev/disk/by-id/raid-isw_cidadbhgaj_TestRAID
==> 	/dev/disk/by-id/raid-isw_cidadbhgaj_TestRAID: unknown volume typ

/lib/udev/vol_id --export /dev/disk/by-id/ata-HDT722516DLA380_VDK91BTC024GGR
==>	ID_FS_USAGE=raid
	ID_FS_TYPE=isw_raid_member
	ID_FS_VERSION=1.1.00
	ID_FS_UUID=
	ID_FS_LABEL=
	ID_FS_LABEL_SAFE=

/lib/udev/vol_id --export /dev/disk/by-id/ata-SAMSUNG_SP0812C_0693J1FWC08152
==>	ID_FS_USAGE=raid
	ID_FS_TYPE=isw_raid_member
	ID_FS_VERSION=1.1.00
	ID_FS_UUID=
	ID_FS_LABEL=
	ID_FS_LABEL_SAFE=

/lib/udev/vol_id --export /dev/disk/by-id/scsi-SATA_HDT722516DLA380_VDK91BTC024GGR
==>	ID_FS_USAGE=raid
	ID_FS_TYPE=isw_raid_member
	ID_FS_VERSION=1.1.00
	ID_FS_UUID=
	ID_FS_LABEL=
	ID_FS_LABEL_SAFE=

/lib/udev/vol_id --export /dev/disk/by-id/scsi-SATA_SAMSUNG_SP0812C0693J1FWC08152
==>	ID_FS_USAGE=raid
	ID_FS_TYPE=isw_raid_member
	ID_FS_VERSION=1.1.00
	ID_FS_UUID=
	ID_FS_LABEL=
	ID_FS_LABEL_SAFE=

I hope this is sufficient. If not, feel free to request more.
Comment 5 Kay Sievers 2006-11-20 21:50:02 UTC 
Please try this in:
   # BIOS Enhanced Disk Device
  -KERNEL=="*[!0-9]", IMPORT{program}="edd_id --export $tempnode"
  +KERNEL=="*[!0-9]", ENV{ID_FS_USAGE}!="raid", IMPORT{program}="edd_id --export $tempnode"

in:
  /etc/udev/rules.d/60-persistent-storage.rules

and see what links are created after reboot.
Comment 7 Andreas Jaeger 2006-11-21 14:10:49 UTC 
Stefan, is #5 helping?
Comment 8 Alexander Osthof 2006-11-21 14:54:55 UTC 
Currently doing a few tests, will provide feedback soon.
Comment 9 Alexander Osthof 2006-11-21 20:13:50 UTC 
Ok, #5 didn't really help with this problem.

But we've made a fix for yast2-bootloader, so now one can install properly to dmraids. A new package of yast2-bootloader will be available, too.

As this fix solves the problem, I close this bug FIXED.