Bug 1726051 - Device cannot be functioning when logout iscsi when doing io, then login in
Summary: Device cannot be functioning when logout iscsi when doing io, then login in
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-02 06:53 UTC by baul
Modified: 2019-07-23 19:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description baul 2019-07-02 06:53:40 UTC
Description of problem:
Logout iscsi when doing io, then login in target which lead that :
1. lsscsi will show the device path as '-'
2. lsblk show the device sda as prev login's device.
3. The device function have change. fio cannot do libaio+direct=1, only libaio+direct=0 But at the beginning before logout,we can do libaio+direct=1 and libaio+direct=0.
4. Even logout/login multple times, the case always be same.
5. We can ls /dev/sda, but when echo 1 > /sys/block/sda/device/delete,
   report that "no such file or dir"
6. Now need reboot system to continue use the /dev/sda in order to test or use the iscsi disk.

Version-Release number of selected component (if applicable):
iscsi-initiator-utils-iscsiuio-6.2.0.874-10.el7.x86_64
iscsi-initiator-utils-6.2.0.874-10.el7.x86_64

3.10.0-957.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
3. The device function have change. fio cannot do libaio+direct=1, only libaio+direct=0 But at the beginning before logout,we can do libaio+direct=1 and libaio+direct=0.
4. Even logout/login multple times, the case always be same.

Expected results:
 Once login ,can continue use the /dev/sda in order to test or use the iscsi disk.
or use another device lable.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.