From: Michael Clark <michael@metaparadigm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "HINCHMAN,PAUL (HP-Roseville,ex1)" <paul_hinchman@hp.com>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: Enterprise patch needed - please help
Date: Thu, 30 May 2002 20:43:18 +0800 [thread overview]
Message-ID: <3CF61E66.1050600@metaparadigm.com> (raw)
In-Reply-To: 1022762307.4123.364.camel@irongate.swansea.linux.org.uk
On 05/30/02 20:38, Alan Cox wrote:
>On Thu, 2002-05-30 at 05:46, Michael Clark wrote:
>
>
>>Also, some devices need a BLIST_SPARSELUN added in scsi_scan.c - even if
>>the device
>>reports SCSI-3, the scanning code by defaults stops when it finds a lun
>>that doesn't
>>respond. It is quite common with enterpise storage to have sparse
>>between luns.
>>
>>
>
>If we use report luns should we even be checking BLIST_SPARSELUN I
>wonder
>
>
>
Oh, is this new or maybe my device doesn't report luns as I've needed
the sparse lun hint even though device was correctly detected as SCSI-3.
This is with 2.4.18
next prev parent reply other threads:[~2002-05-30 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 23:23 Enterprise patch needed - please help HINCHMAN,PAUL (HP-Roseville,ex1)
2002-05-30 0:41 ` Alan Cox
2002-05-30 4:46 ` Michael Clark
2002-05-30 12:38 ` Alan Cox
2002-05-30 12:43 ` Michael Clark [this message]
2002-05-30 14:40 ` Andrew Patterson
2002-05-30 17:30 ` Mounting multiple LUNs on a single SCSI device Alan Dayley
2002-05-30 19:07 ` Kurt Garloff
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 16:33 Enterprise patch needed - please help HINCHMAN,PAUL (HP-Roseville,ex1)
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=3CF61E66.1050600@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=paul_hinchman@hp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.