+1
−0
+1
−1
+17
−13
Loading
SCSI/iSCSI triggers bdev_scsi_reset() in two reasons: - mgmt command from initiator side - target side cleanup For example, once we hit the following logs: nvme_ctrlr.c:1639:nvme_ctrlr_disconnect: *NOTICE*: [0000:b2:00.0] resetting controller bdev_nvme.c:2027:_bdev_nvme_reset_ctrlr_complete: *NOTICE*: Resetting controller successful. We need to know why the bdev/nvme resets, rather than a single SPDK_SCSI_TASK_FUNC_LUN_RESET reason, separate it into two to distinguish the root cause of the lower layer bdev reset. Change-Id: I087add31c31e46780c6e7c60cc8af14290e84636 Signed-off-by:zhenwei pi <pizhenwei@bytedance.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20361 Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Jim Harris <jim.harris@samsung.com> Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com>