From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>,
Mike Christie <michaelc@cs.wisc.edu>,
Christoph Hellwig <hch@infradead.org>,
"K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
ohering@suse.com, jbottomley@parallels.com,
linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that may have been removed.
Date: Fri, 29 Aug 2014 09:39:26 +0200 [thread overview]
Message-ID: <54002E2E.7030301@acm.org> (raw)
In-Reply-To: <54001B5F.9040506@suse.de>
On 08/29/14 08:19, Hannes Reinecke wrote:
> On 08/29/2014 04:42 AM, Mike Christie wrote:
>> How are distros handling 0x6/0x3f/0x0e (report luns changed) when it
>> gets passed to userspace? Is everyone kicking off a new full (add and
>> delete) scan to handle this or logging it? Is the driver returning this
>> when the LUNs change?
>>
> Currently it's logged to userspace and ignored.
> Doing an automated rescan has proven to be dangerous, as it
> might disconnect any LUNs which are still in use by applications.
> Especially HA or database setups tends to become very annoyed
> when you do an automated rescan.
Has it already been considered to add newly discovered LUNs
automatically and to leave it to the user to remove stale LUNs manually
? That would be similar to what the rescan-scsi-bus.sh script does
without option -r/--remove.
Bart.
next prev parent reply other threads:[~2014-08-29 7:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 3:09 [PATCH 0/2] Drivers: scsi: storvsc: Fix issues with hot-add/remove of LUNs K. Y. Srinivasan
2014-08-17 3:09 ` K. Y. Srinivasan
2014-08-17 3:09 ` [PATCH 1/2] Drivers: scsi: storvsc: In responce to a scan event, scan the host K. Y. Srinivasan
2014-08-17 3:09 ` K. Y. Srinivasan
2014-08-17 3:09 ` [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that may have been removed K. Y. Srinivasan
2014-08-17 3:09 ` K. Y. Srinivasan
2014-08-19 17:54 ` Christoph Hellwig
2014-08-19 17:54 ` Christoph Hellwig
2014-08-26 22:54 ` KY Srinivasan
2014-08-26 22:54 ` KY Srinivasan
2014-08-29 1:11 ` Christoph Hellwig
2014-08-29 1:11 ` Christoph Hellwig
2014-08-27 14:31 ` Hannes Reinecke
2014-08-27 14:31 ` Hannes Reinecke
2014-08-29 2:42 ` Mike Christie
2014-08-29 6:19 ` Hannes Reinecke
2014-08-29 6:19 ` Hannes Reinecke
2014-08-29 7:39 ` Bart Van Assche [this message]
2014-08-29 8:13 ` Hannes Reinecke
2014-08-29 8:13 ` Hannes Reinecke
2014-08-29 13:53 ` James Bottomley
2014-08-29 13:53 ` James Bottomley
2014-08-29 15:01 ` Ewan Milne
2014-08-29 15:01 ` Ewan Milne
2014-09-25 13:47 ` [PATCH 0/2] Drivers: scsi: storvsc: Fix issues with hot-add/remove of LUNs Christoph Hellwig
2014-09-29 1:47 ` KY Srinivasan
2014-09-29 1:47 ` KY Srinivasan
2014-10-07 17:44 ` KY Srinivasan
2014-10-07 17:44 ` KY Srinivasan
2014-10-17 13:22 ` Christoph Hellwig
2014-10-17 13:22 ` Christoph Hellwig
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=54002E2E.7030301@acm.org \
--to=bvanassche@acm.org \
--cc=devel@linuxdriverproject.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michaelc@cs.wisc.edu \
--cc=ohering@suse.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.