From: david@lang.hm
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: Re: deterministic scsi order with async scan
Date: Thu, 16 Jul 2009 10:23:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0907161022540.9159@asgard> (raw)
In-Reply-To: <20090716115703.GQ24310@parisc-linux.org>
On Thu, 16 Jul 2009, Matthew Wilcox wrote:
> On Wed, Jul 15, 2009 at 06:09:22PM -0700, david@lang.hm wrote:
>> is there any way to get deterministic device ordering with scsi async
>> scanning?
>>
>> currently (2.6.30) it seems that the various scsi busses are loaded in
>> the order that they are detected, which can vary from boot to boot
>> depending on how long it takes for the card to initialize.
>
> I think you're confused. The async scsi scanning was designed to _not_
> move devices around randomly. There are other asynchronous schemes in
> the kernel, some of which were not designed with the same care.
>
> The SCSI async scan can't do much about it if the busses are detected
> in a different order.
>
>> would it be possible to detect the cards/drives, but not register them
>> until all the detection is complete so that they can be registered in a
>> deterministic order?
>
> That's exactly how the scsi async scanning works.
hmm, in that case how can I troubleshoot why this system is detecting the
two different PCI-E cards in different orders on different boots.
David Lang
>> having two drives on two different controllers swap positions from boot
>> to boot makes it very painful. yes I can make an initrd that fixes this
>> up in user space by examining each drive and creating links to re-order
>> them, but this is a lot of work to fix randomization that can be
>> prevented in the first place.
>>
>> David Lang
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2009-07-16 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 1:09 david
2009-07-16 11:33 ` Boaz Harrosh
2009-07-16 17:22 ` david
2009-07-16 18:32 ` James Smart
2009-07-16 18:43 ` david
2009-07-16 19:39 ` James Bottomley
2009-07-16 19:48 ` david
2009-07-16 19:56 ` James Bottomley
2009-07-16 20:59 ` david
2009-07-16 19:58 ` Boaz Harrosh
2009-07-16 20:05 ` Matthew Wilcox
2009-07-16 19:53 ` Boaz Harrosh
2009-07-16 11:57 ` Matthew Wilcox
2009-07-16 17:23 ` david [this message]
2009-07-16 18:15 ` Matthew Wilcox
2009-07-16 18:31 ` david
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=alpine.DEB.1.10.0907161022540.9159@asgard \
--to=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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
all inboxes | Powered by JetHome®