summaryrefslogtreecommitdiff
path: root/drivers/scsi/ibmvscsi
diff options
context:
space:
mode:
authorlijinlin <lijinlin3@huawei.com>2021-07-27 11:44:55 +0800
committerMartin K. Petersen <martin.petersen@oracle.com>2021-07-29 21:58:35 -0400
commitf0f82e2476f6adb9c7a0135cfab8091456990c99 (patch)
treea59189d4d303a8b7e84c4922e4b0b21116843a08 /drivers/scsi/ibmvscsi
parent5c04243a56a7977185b00400e59ca7e108004faf (diff)
scsi: core: Fix capacity set to zero after offlinining device
After adding physical volumes to a volume group through vgextend, the kernel will rescan the partitions. This in turn will cause the device capacity to be queried. If the device status is set to offline through sysfs at this time, READ CAPACITY command will return a result which the host byte is DID_NO_CONNECT, and the capacity of the device will be set to zero in read_capacity_error(). After setting device status back to running, the capacity of the device will remain stuck at zero. Fix this issue by rescanning device when the device state changes to SDEV_RUNNING. Link: https://lore.kernel.org/r/20210727034455.1494960-1-lijinlin3@huawei.com Reviewed-by: Bart Van Assche <bvanassche@acm.org> Signed-off-by: lijinlin <lijinlin3@huawei.com> Signed-off-by: Wu Bo <wubo40@huawei.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/ibmvscsi')
0 files changed, 0 insertions, 0 deletions