lkml.org 
[lkml]   [2014]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that may have been removed.
Date


> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@infradead.org]
> Sent: Tuesday, August 19, 2014 10:55 AM
> To: KY Srinivasan
> Cc: hare@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; ohering@suse.com;
> jbottomley@parallels.com; linux-scsi@vger.kernel.org; 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 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 for an I/O to remove the device, force the
> > discovery of LUNs that may have been removed prior to discovering LUNs
> > that may have been added.
>
> 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 checked in.

Regards,

K. Y



\
 
 \ /
  Last update: 2014-08-27 01:01    [W:0.107 / U:0.708 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site