All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <JBottomley@parallels.com>
Cc: michaelc@cs.wisc.edu, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi scan: don't fail scans when host is in recovery
Date: Wed, 22 Feb 2012 10:56:58 +0100	[thread overview]
Message-ID: <4F44BBEA.3020400@suse.de> (raw)
In-Reply-To: <1314250598-2852-1-git-send-email-michaelc@cs.wisc.edu>

On 08/25/2011 07:36 AM, michaelc@cs.wisc.edu wrote:
> From: Mike Christie <michaelc@cs.wisc.edu>
> 
> The problem is that if we are doing a scsi scan then the device goes
> into recovery then we will wait for the recovery to complete. It waits
> because scsi-ml will send inquiries or report luns and the queueing code
> will have been blocked due to the host not being ready. However, if we
> are in recovery and then a scan is started the scan will silently fail
> and some devices will not be added.
> 
> It is easy to hit the problem where devices do not show up with
> FC where we are doing tests that disrupt the target controllers.
> When the controller is disruprted (reboot, or setting firmware, etc),
> and we cause the dev loss tmo to fire then devices will be removed
> Then when the problem has been fixed, the rport will be scanned and
> devices should be added back. But if we cause another disruption before
> scanning has started then devices will not get added back. If the problem
> is not started until the scan is started then the devices will be added
> back.
> 
> This patch fixes that problem by not failing scans when the host
> is in recovery. We will let scsi-ml send the IO and let the queueing
> and scsi error handling deal with it like is done if we went into
> recovery while scanning.
> 
> For recovery cases where the host is being torn down then with the
> patch we will still fail the scan since there is not point in scanning.
> 
> Patch was made and tested over scsi-misc.
> 
> 
> Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
> ---
>  include/scsi/scsi_host.h |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/include/scsi/scsi_host.h b/include/scsi/scsi_host.h
> index f1f2644..22b7b23 100644
> --- a/include/scsi/scsi_host.h
> +++ b/include/scsi/scsi_host.h
> @@ -791,7 +791,8 @@ static inline struct device *scsi_get_device(struct Scsi_Host *shost)
>   **/
>  static inline int scsi_host_scan_allowed(struct Scsi_Host *shost)
>  {
> -	return shost->shost_state == SHOST_RUNNING;
> +	return shost->shost_state == SHOST_RUNNING ||
> +	       shost->shost_state == SHOST_RECOVERY;
>  }
>  
>  extern void scsi_unblock_requests(struct Scsi_Host *);

James, ping?
Any reason it was not included?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
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

  reply	other threads:[~2012-02-22  9:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  5:36 [PATCH 1/1] scsi scan: don't fail scans when host is in recovery michaelc
2012-02-22  9:56 ` Hannes Reinecke [this message]
2012-02-22 20:45   ` Mike Christie
2012-02-23  7:21     ` Hannes Reinecke

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=4F44BBEA.3020400@suse.de \
    --to=hare@suse.de \
    --cc=JBottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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.