From: Kurt Garloff <garloff@suse.de>
To: Linux SCSI list <linux-scsi@vger.kernel.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Andrew Morton <akpm@osdl.org>
Subject: Patches for SCSI scanning
Date: Sun, 18 Apr 2004 20:57:51 +0200 [thread overview]
Message-ID: <20040418185751.GC4868@tpkurt.garloff.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hi,
at SUSE, the way that Linux scan SCSI devices has constantly generated
a certain support load. Not extremely but still astonishing.
As a consequence, we have created a number of patches to our 2.4 kernels
that did improve some things, such as the backport of the REPORT_LUNS
scanning from 2.6 and a number of boot/module parameters that allowed
users to influence how the scanning is done.
http://www.suse.de/~garloff/Linux/scsi-scan/scsi-scanning.html
With kernel 2.6, the REPORT_LUNS is standard for SCSI-3 devices,
but still many arrays exist that report as SCSI-2 and will require
BLIST_SPARSELUN|BLIST_LARGELUN.
An alternative to the blacklist is to offer boot/module parameters
again. This is what the following series of 6 patches do.
Most don't really depend on each other, but they'll only apply
cleanly in the order sent.
I did not yet compare our 2.4 blacklist with the 2.6 one; I'll
port our additional 2.4 entries to 2.6 soon.
Regards,
--
Kurt Garloff <garloff@suse.de> Cologne, DE
SUSE LINUX AG, Nuernberg, DE SUSE Labs (Head)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-04-18 19:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 18:57 Kurt Garloff [this message]
2004-04-18 23:16 ` Patches for SCSI scanning James Bottomley
2004-04-20 11:54 ` Kurt Garloff
2004-04-20 12:04 ` Christoph Hellwig
2004-04-20 13:02 ` Kurt Garloff
2004-04-20 14:38 ` James Bottomley
2004-04-20 16:03 ` Kurt Garloff
2004-04-20 16:08 ` James Bottomley
2004-04-21 13:48 ` Kurt Garloff
2004-04-21 15:36 ` James Bottomley
2004-04-21 13:45 ` Kurt Garloff
2004-04-21 14:10 ` PATCH 1/5: scsi-scan-deprecate-forcelun Kurt Garloff
2004-04-21 14:12 ` PATCH 2/5: scsi-scan-blist_replun Kurt Garloff
2004-04-21 15:14 ` Christoph Hellwig
2004-04-21 15:30 ` Kurt Garloff
2004-04-21 16:03 ` Kurt Garloff
2004-04-21 14:13 ` PATCH 3/5: scsi-scan-no-offl-pq-notcon Kurt Garloff
2004-04-21 14:14 ` PATCH 4/5: scsi-scan-dont-att-pq-notcon Kurt Garloff
2004-04-21 15:02 ` Christoph Hellwig
2004-04-21 15:24 ` Kurt Garloff
2004-04-21 15:33 ` Mike Anderson
2004-04-21 15:33 ` Christoph Hellwig
2004-04-21 16:08 ` Kurt Garloff
2004-04-21 16:18 ` James Bottomley
2004-04-21 16:55 ` Patrick Mansfield
2004-04-21 22:51 ` Kurt Garloff
2004-04-22 20:39 ` Patrick Mansfield
2004-04-22 20:45 ` James Bottomley
2004-04-21 16:58 ` Kurt Garloff
2004-04-21 16:16 ` Kurt Garloff
2004-04-21 15:40 ` James Bottomley
2004-04-21 14:14 ` PATCH 5/5: scsi-scan-inq-timeout Kurt Garloff
2004-04-21 20:24 ` Patrick Mansfield
2004-04-21 22:48 ` Kurt Garloff
2004-04-21 23:49 ` Patrick Mansfield
2004-04-20 16:26 ` Patches for SCSI scanning Patrick Mansfield
2004-04-20 16:42 ` Kurt Garloff
2004-04-20 17:44 ` Patrick Mansfield
2004-04-21 13:52 ` Kurt Garloff
2004-04-20 10:24 ` Fabien Salvi
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 4:09 Martin Peschke3
2004-04-22 4:17 Martin Peschke3
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=20040418185751.GC4868@tpkurt.garloff.de \
--to=garloff@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--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