public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Wright <timw@splhi.com>
To: Nathan Walp <faceprint@faceprint.com>
Cc: David Balazic <david.balazic@uni-mb.si>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac20
Date: Tue, 13 Mar 2001 15:02:21 -0800	[thread overview]
Message-ID: <20010313150221.A2524@kochanski.internal.splhi.com> (raw)
In-Reply-To: <3AAE4DB6.8349ACBA@uni-mb.si> <3AAE7406.283D2411@faceprint.com>
In-Reply-To: <3AAE7406.283D2411@faceprint.com>; from faceprint@faceprint.com on Tue, Mar 13, 2001 at 02:24:54PM -0500

On Tue, Mar 13, 2001 at 02:24:54PM -0500, Nathan Walp wrote:
> David Balazic wrote:
> > 
> > SCSI adapters are enumerated randomly(*) , relying on certain numbering
> > will get you into trouble, sooner or later.
> > There is no commonly accepted solution, AFAIK.
> > The same thing can happent to disk enumeration ( sdb becomes sdc )
> > or partition enumeration ( hda6 becomes hda5 ).
> > 
> > * - theoreticaly no, but practicaly yes ( most of the time )
> 
> SCSI adapters are given host numbers in a random order?  Even with no
> hardware changes?  Does this make less than sense to anyone else?  Every
> kernel EVER up till now has had the real scsi cards (in some particular
> order) then ide-scsi.  Have I just been lucky???
> 

No, it's not truly random. That would be insane. And, no, if you don't change
the kernel or the hardware, then they won't jump around.
But, yes, if you change the hardware, or someone changes the probe order
in the kernel, you can suffer from device name slippage. This is a minor
problem on a small home system, and a massive PITA on a large server.
You can at least mandate the probe order on a 2.4 system (see the scsihosts
parameter).

Tim

-- 
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI

  reply	other threads:[~2001-03-13 23:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-13 16:41 Linux 2.4.2ac20 David Balazic
2001-03-13 19:24 ` Nathan Walp
2001-03-13 23:02   ` Tim Wright [this message]
2001-03-14  9:31   ` David Balazic
2001-03-14 15:12     ` Nathan Walp
2001-03-14 15:36       ` magic device renumbering was -- " John Jasen
2001-03-14 16:27         ` Tim Wright
2001-03-14 18:15           ` Greg KH
2001-03-15  1:53             ` Tim Wright
2001-03-15  2:08               ` Greg KH
2001-03-14 18:23         ` Christoph Hellwig
2001-03-14 18:45           ` Peter Svensson
2001-03-14 19:11           ` Lars Kellogg-Stedman
2001-03-14 19:34             ` Andreas Dilger
2001-03-14 19:44             ` Richard B. Johnson
2001-03-15 13:46               ` John Jasen
2001-03-14 20:01             ` Christoph Hellwig
2001-03-16  9:11             ` Stephen C. Tweedie
2001-03-14 19:16           ` Andreas Dilger
2001-03-14 20:08           ` John Jasen
2001-03-15  3:04         ` Stephen Degler
  -- strict thread matches above, loose matches on Subject: below --
2001-03-13 23:46 Wayne.Brown
2001-03-13 23:41 Douglas Gilbert
2001-03-13  4:36 Alan Cox
2001-03-13  6:28 ` Nathan Walp
2001-03-13 23:17 ` Michal Jaegermann
2001-03-13 23:38   ` Jeff Garzik

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=20010313150221.A2524@kochanski.internal.splhi.com \
    --to=timw@splhi.com \
    --cc=david.balazic@uni-mb.si \
    --cc=faceprint@faceprint.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