From: Matt Ryan <matt@sigmastorage.com>
To: linux-kernel@vger.kernel.org
Subject: device name switching
Date: Thu, 26 Jul 2001 22:02:51 -0700 [thread overview]
Message-ID: <3B60F5FB.AB29B413@sigmastorage.com> (raw)
[ please CC responses to me ]
hello -
if I have two hard drives /dev/hda and /dev/hdc, and I pull out the
first drive (root partition is raid1 for redundant boot), on reboot I am
left with just /dev/hdc. this would seem like the normal, anticipated
behavior.
however, if I stick in a couple of drives connected to a Promise Ultra
100 card and try the same sort of thing, the drive name assignments
reliably are changed. if I start with /dev/hd[aceg] (e and g on the
promise card), and pull out hdc, on reboot I have /dev/hd[ace]. if I
start with /dev/hd[aceg] and pull out hda, I also end up with
/dev/hd[ace]. the higher drives sort of collapse down to fill the
'hole.' this behavior has been reproducible through a series of 2.4
kernels, the last I've tried is 2.4.5.
my question is, is this anticipated behavior, or does this surprise
anybody? for all I know the BIOS decides the assignments and the kernel
has nothing to do with it (also this is an intel d815eea2 chipset,
though I'm pretty sure I've seen the same behavior on a Sis-based
chipset as well).
another reminiscent problem (but probably totally unrelated), is the
name assigned to NICs. in a box with the same intel motherboard, with
one onboard nic (eepro100) and one PCI nic (3C905C), I have a 2.4.3
kernel and a 2.4.7 kernel. each kernel has the opposite idea of which
card is eth0 and which is eth1. curious...
Matt
reply other threads:[~2001-07-27 5:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B60F5FB.AB29B413@sigmastorage.com \
--to=matt@sigmastorage.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox