From: linas@austin.ibm.com (Linas Vepstas)
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-hotplug-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Alexander E. Patrakov" <patrakov@ums.usu.ru>,
linux-scsi@vger.kernel.org,
Patrick Mansfield <patmans@us.ibm.com>
Subject: Re: Asynchronous scsi scanning, version 9
Date: Mon, 26 Jun 2006 20:58:32 +0000 [thread overview]
Message-ID: <20060626205832.GC10505@austin.ibm.com> (raw)
In-Reply-To: <1151270127.3617.26.camel@mulgrave.il.steeleye.com>
On Sun, Jun 25, 2006 at 04:15:26PM -0500, James Bottomley wrote:
> On Thu, 2006-06-01 at 07:23 -0600, Matthew Wilcox wrote:
>
> > There's a potential solution to this. If we add a hook to sys_module_init
> > such that it'll call a specified function before returning, we can make
> > it wait until all scans are done. This way, userspace never sees the
> > asynchronous scanning behaviour. But if you have devices of different
> > types, you won't get the overlapping scans.
>
> How about this solution which works for me with debian on a huge 6 bus
> scsi machine: it introduces a new module scsi_wait_scan.ko whose sole
> job is to wait for the scans to complete in its init function. The
> initrd/initramfs sequence now becomes:
>
> insert all other modules
> modprobe scsi_wait_scan
I guess there's no way of figuring out where the root disk is, and
waiting only for that?
On large servers, there may be hundreds of attached disks. Anything which
can parallelize and perform an async scan will help boot times; however,
waiting for all disks to come on-line when only one is actually needed can
cause trouble.
In particular, some of the attached disks/scsi chains may be bad,
in which case one has to wait for a tediously long device/bus/host reset
sequence to complete, and off-line the broken disk.
--linas
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-06-26 20:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060511143352.GI12272@parisc-linux.org>
[not found] ` <20060518172258.GL1604@parisc-linux.org>
[not found] ` <20060529031915.GB23405@parisc-linux.org>
[not found] ` <447AB2F5.2000700@s5r6.in-berlin.de>
[not found] ` <20060529130515.GE23405@parisc-linux.org>
2006-05-31 23:21 ` Asynchronous scsi scanning, version 9 Patrick Mansfield
2006-06-01 12:22 ` Kay Sievers
2006-10-26 19:53 ` maximilian attems
2006-06-01 13:14 ` Alexander E. Patrakov
2006-06-01 13:21 ` maximilian attems
2006-06-01 13:23 ` Matthew Wilcox
2006-06-01 13:26 ` Alexander E. Patrakov
2006-06-01 14:00 ` Arjan van de Ven
2006-06-25 21:15 ` James Bottomley
2006-06-25 22:46 ` Matthew Wilcox
2006-06-26 8:24 ` Arjan van de Ven
2006-06-26 12:40 ` Matthew Wilcox
2006-06-26 12:59 ` Arjan van de Ven
2006-06-26 16:03 ` Greg KH
2006-06-26 14:44 ` Matthew Dharm
2006-06-26 15:18 ` Matthew Wilcox
2006-06-26 15:44 ` James Bottomley
2006-06-26 16:02 ` Greg KH
2006-06-26 21:08 ` Matthew Dharm
2006-06-26 22:15 ` Matthew Wilcox
2006-06-26 18:55 ` [SPAM] " Doug Ledford
2006-06-26 21:04 ` Matthew Dharm
2006-06-26 21:20 ` Doug Ledford
2006-06-26 20:58 ` Linas Vepstas [this message]
2006-06-26 21:14 ` James Bottomley
2006-06-26 21:21 ` Linas Vepstas
2006-06-26 21:41 ` James Bottomley
2006-06-28 7:52 ` Hannes Reinecke
2006-06-28 16:03 ` 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=20060626205832.GC10505@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=patmans@us.ibm.com \
--cc=patrakov@ums.usu.ru \
--cc=stefanr@s5r6.in-berlin.de \
/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).