On 08/29/2014 04:42 AM, Mike Christie wrote:
On 08/27/2014 09:31 AM, Hannes Reinecke wrote:
On 08/19/2014 07:54 PM, Christoph Hellwig wrote:
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The only way a guest
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
On 08/29/2014 09:39 AM, Bart Van Assche wrote:
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
On Fri, 2014-08-29 at 10:13 +0200, Hannes Reinecke wrote:
On 08/29/2014 09:39 AM, Bart Van Assche wrote:
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
On Thu, 2014-08-28 at 21:42 -0500, Mike Christie wrote:
On 08/27/2014 09:31 AM, Hannes Reinecke wrote:
On 08/19/2014 07:54 PM, Christoph Hellwig wrote:
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The
On Tue, Aug 26, 2014 at 10:54:51PM +, KY Srinivasan wrote:
This looks pretty reasonable to me, but I wonder if we should move this up
to common code so that it happens for any host rescan triggered by sysfs or
other drivers as well.
Ping. Any decision on if/when this patch may be
On 08/27/2014 09:31 AM, Hannes Reinecke wrote:
On 08/19/2014 07:54 PM, Christoph Hellwig wrote:
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The only way a guest can identify the removed LUN is when an I/O is
On 08/19/2014 07:54 PM, Christoph Hellwig wrote:
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The only way a guest can identify the removed LUN is when an I/O is
attempted on a removed LUN - the SRB status code
; Martin K. Petersen
Subject: Re: [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that
may have been removed.
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The only way a guest can identify
On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
The host asks the guest to scan when a LUN is removed or added.
The only way a guest can identify the removed LUN is when an I/O is
attempted on a removed LUN - the SRB status code indicates that the LUN
is invalid. We currently
The host asks the guest to scan when a LUN is removed or added.
The only way a guest can identify the removed LUN is when an I/O is
attempted on a removed LUN - the SRB status code indicates that the LUN
is invalid. We currently handle this SRB status and remove the device.
Rather than waiting
11 matches
Mail list logo
