From: Billy Crook <billycrook@gmail.com>
To: Caspar Smit <c.smit@truebit.nl>
Cc: "Desai, Kashyap" <Kashyap.Desai@lsi.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Moore, Eric" <Eric.Moore@lsi.com>,
"Prakash, Sathya" <Sathya.Prakash@lsi.com>
Subject: Re: mpt2sas: bug in disk ordering?
Date: Fri, 13 May 2011 07:03:55 -0500 [thread overview]
Message-ID: <BANLkTinsvVTfsJJVRU3o6S7HiOh5RwU9_Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikaFkeEaTPutOuMAnUx5gvdP=JyJQ@mail.gmail.com>
On Fri, May 13, 2011 at 06:46, Caspar Smit <c.smit@truebit.nl> wrote:
> But when i use a LSI 3081E-R HBA (mptsas driver) the disk ordering is
> ALWAYS the same, and always in correct order.
> I would like to keep that functionality when upgrading to the newer 9211-8i HBA.
That was an unintentional coincidence. Consider yourself lucky nothing
was destroyed during the time you assumed it was deterministic. Disk
ordering is essentially random in Linux, and will continue to be,
indefinitely. If being able to refer to specific disks is important,
use the links in /dev/disk/ or assign the disks LABELs and use those
or UUIDs. If /dev/disk is gone or not working, that is the problem
you need to solve, NOT disk startup order.
next prev parent reply other threads:[~2011-05-13 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 9:19 mpt2sas: bug in disk ordering? Caspar Smit
2011-05-13 10:34 ` Caspar Smit
2011-05-13 10:37 ` Arne Jansen
2011-05-13 10:41 ` Caspar Smit
2011-05-13 10:51 ` Arne Jansen
2011-05-13 10:56 ` Caspar Smit
2011-05-13 11:15 ` Desai, Kashyap
2011-05-13 11:46 ` Caspar Smit
2011-05-13 12:03 ` Billy Crook [this message]
2011-05-13 12:05 ` Caspar Smit
2011-05-13 12:09 ` Mikael Abrahamsson
2011-05-13 14:39 ` James Bottomley
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=BANLkTinsvVTfsJJVRU3o6S7HiOh5RwU9_Q@mail.gmail.com \
--to=billycrook@gmail.com \
--cc=Eric.Moore@lsi.com \
--cc=Kashyap.Desai@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=c.smit@truebit.nl \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).