All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Hannes Reinecke <hare@suse.de>,
	Brian King <brking@linux.vnet.ibm.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: SCSI scanning behavior
Date: Wed, 26 Aug 2015 06:52:45 -0700	[thread overview]
Message-ID: <55DDC4AD.6040804@sandisk.com> (raw)
In-Reply-To: <55DDB8F3.3020308@suse.de>

On 08/26/15 06:02, Hannes Reinecke wrote:
> On 08/21/2015 12:11 AM, Brian King wrote:
>> However, I'm still left wondering why we are adding PQ=1, PDT=0 devices in the sequential LUN scan at all.
>> Are there media changer devices out there that we've seen respond like this? Even so, does it make sense
>> to add PQ=1, PDT=0 LUNs for LUN > 0?
>>
> Yes, unfortunately we need this. NetApp arrays have a habit of
> returning 'PQ=1' for unconnected LUN 0, even though higher LUNs are
> present. So we need to add devices for PQ=1, otherwise we wouldn't
> be able to scan them.
> We _might_ be able to tweak this by ignoring devices with PQ=1 and
> LUN!=0; however, it might break other things.

Hello Hannes,

The code in scsi_scan.c already skips LUNs with PQ=1 and PDT=0x1f. I'm 
not sure we should skip LUNS with PQ=1 and a PDT value other than 0x1f.

Thanks,

Bart.


  reply	other threads:[~2015-08-26 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 22:11 SCSI scanning behavior Brian King
2015-08-26 13:02 ` Hannes Reinecke
2015-08-26 13:52   ` Bart Van Assche [this message]
2015-09-02 14:31   ` [PATCH] SCSI: Scale up REPORT_LUNS timeout on failure Brian King
2015-09-04 15:00     ` Bart Van Assche
2015-09-04 15:28       ` Brian King
2015-09-04 15:36     ` James Bottomley
2015-09-04 15:47       ` Brian King
2015-09-04 16:15         ` James Bottomley
2015-09-04 19:47           ` [PATCH] SCSI: Increase REPORT_LUNS timeout Brian King
2015-09-13  8:43             ` Hannes Reinecke
2015-11-03  4:03             ` Martin K. Petersen

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=55DDC4AD.6040804@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=hare@suse.de \
    --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 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.