Summary: | udev inaccurat device mapping | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bjoern Olausson <contactme> |
Component: | New packages | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | RESOLVED WONTFIX | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bjoern Olausson
2005-04-11 16:18:45 UTC
sys-fs/mdadm requires no /etc/raidtab, basically it requires no configuration file at all for most purposes... Otherwise, you must set partition type to fd with both mdadm and raidtools for autodetection to work, why don sys-fs/mdadm requires no /etc/raidtab, basically it requires no configuration file at all for most purposes... Otherwise, you must set partition type to fd with both mdadm and raidtools for autodetection to work, why don´t you do this? See http://www.tldp.org/HOWTO/Software-RAID-HOWTO-7.html#ss7.2 I did! here's my raidtab and so I created the raid. But still autodetection does not work. But that problem does not change the stupid devicenaming from udev. I am now hunting down my bug in creating the RAID. # /filing (RAID 1) smaller disk is disk 0 raiddev /dev/md0 raid-level 1 nr-raid-disks 2 chunk-size 32 persistent-superblock 1 device /dev/sdd1 raid-disk 0 device /dev/sdc1 raid-disk 1 The raid problem is found: Kernel cannot detect anything because the hipoint module hpt374 is loadet as module... So there's no sens with autodetection and this is why I ran into this. So one more reason for devlabl regards Bjoern If you need to boot from RAID-1 then don If you need to boot from RAID-1 then don´t compile the IDE controller driver as a module. No devlabels would solve this, I can´t see your point. How would devlabel fix a problem with kernel missing an IDE driver when it needs it and not seeing those disks at all? If you don´t boot from RAID then I don´t understand your problem. Autodetect works once the module is loaded. I am not booting from the raid! And I don't want to build an initrd for the driver (the driver is not included in the kernel it's an external driver from highpoint) I created my arry according to the tlp howto... autodetection will not work. But that is not the primary problem why I issued this bug. Every fstab entry will be messed up when I boot with a attqached USB drive or add an extra hard disc to the controller. And there is no way to write rules for identical drives except the partition UUID which immho is not supported by hotplug or sysfs or udev by default. regards blubbi PS.: forgett the raid problem it might be stupid idea to mention it here.. but as you see, you can run in trouble when autodetection woun't work. Well, if you have problems after adding another drive, then I would suggest that you should use /dev/ide/hostX/busX/targetX/lunX/partX or /dev/scsi/hostX/busX/targetX/lunX/partX instead of /dev/hdaX or /dev/sdaX in /etc/fstab and /etc/raidtab. devlabel isn't needed, you can always write a custom udev rule to always keep your disks in the same place. I'm closing this bug because of this. And, you can always use devfs if you really like it... |