Skip to contentSkip to conversation

Linux not adhering to BIOS Drive boot order?

DISCUSSION David Balazic 3 participants 4 messages Jan 18, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines · Tim Fletcher
Quoted 3 lines

How does MD/RAID0 know which array should be /dev/md0? What if you had a second array on /dev/hdb and /dev/hdd, would that become /dev/md0 (assuming it had a kernel/boot sector)?

/etc/raidtab specifies which drives belong in which array, but I only have
hda and hdc so I can't really answer the question

What happens if /dev/md0 is /dev/sda and /dev/sdc ( the system also has sdb )
and sda fails or is removed ?
the old sdb will now be sda and old-sdc will be sdb.
md0 will look into sda , which is now the non-md disk , and sdc , which doesn't exists any more ???

Signature · 8 lines
David Balazic
--------------
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#1 lore raw
Quoted 7 lines
Quoted 6 lines
Quoted 3 lines

How does MD/RAID0 know which array should be /dev/md0? What if you had a second array on /dev/hdb and /dev/hdd, would that become /dev/md0 (assuming it had a kernel/boot sector)?

/etc/raidtab specifies which drives belong in which array, but I only have
hda and hdc so I can't really answer the question

Quoted 6 lines

What happens if /dev/md0 is /dev/sda and /dev/sdc ( the system also has sdb )
and sda fails or is removed ?
the old sdb will now be sda and old-sdc will be sdb.
md0 will look into sda , which is now the non-md disk , and sdc , which doesn't exists any more ???

This is when devfs comes into its own, as the disks are refered to by their device/controller id not by the /dev/sd{a,b,c,etc} numbering, hence when one fails the others don't change. Also I think the kernel autodetect code for scsi devices will deal with this case, but I'm not sure.

Signature · 14 lines
   Tim Fletcher - Network manager   .~.
                                    /V\      L   I   N   U   X
     [email protected]        // \\  >Don't fear the penguin<
[email protected]   /(   )\
 irc: Night-Shade on quakenet      ^^-^^

Catapultam habeo. Nisi pecuniam omnem mihi dabis, ad caput tuum saxum
immane mittam (For non-latiners: "I have a catapult. Give me all the
money, or I will fling an enormous rock at your head.")

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#2 lore raw
Quoted 4 lines · Tim Fletcher

This is when devfs comes into its own, as the disks are refered to by their device/controller id not by the /dev/sd{a,b,c,etc} numbering, hence when one fails the others don't change. Also I think the kernel autodetect code for scsi devices will deal with this case, but I'm not sure.

'would be great to use driver name, e.g. something like /dev/scsi/advansys/... (I don't remember devfs naming scheme)

Xav

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#3 lore raw
Quoted 7 lines
Quoted 4 lines

This is when devfs comes into its own, as the disks are refered to by their device/controller id not by the /dev/sd{a,b,c,etc} numbering, hence when one fails the others don't change. Also I think the kernel autodetect code for scsi devices will deal with this case, but I'm not sure.

'would be great to use driver name, e.g. something like /dev/scsi/advansys/... (I don't remember devfs naming scheme)

Then you are back to the arguement about should the naming be based on the function of the device (scsi0,1,2 / eth0,1,2) or based on the hardware (aic7xxx0,1,2 advansys0,1,2 / tulip0,1,2 eepro0,1,2). *BSD uses this naming scheme for its ethernet interfaces, not sure about its scsi thou.

I prefer the functional naming scheme (scsi0 / eth0) as I can change the hardware in a machine and not change anything in the init scripts, assuming the driver is in kernel or if not I only need to change the line /etc/modules.conf.

Signature · 12 lines
   Tim Fletcher - Network manager   .~.
                                    /V\      L   I   N   U   X
     [email protected]        // \\  >Don't fear the penguin<
[email protected]   /(   )\
 irc: Night-Shade on quakenet      ^^-^^

"I am Homer of Borg.  Prepare to Oooh! Doughnuts!"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/