Skip to contentSkip to conversation

New: mysterious block devices are shown under /dev folder

Bug 216232 [email protected] 2 participants 4 messages Jul 10, 2022 – Jul 15, 2022 SCSI

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=216232

Bug ID: 216232
Summary: mysterious block devices are shown under /dev folder
Product: SCSI Drivers
Version: 2.5
Kernel Version: 5.4.61
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: QLOGIC QLA2XXX
Assignee: [email protected]
Reporter: [email protected]
Regression: No

we are using linux kernel 5.4.61 and fibre channel card is qlogic's ISP2722-based 16/32Gb adapter card.

the problem is that we are seeing some devices with lun 768 with size of 512B shown under /dev folder. In the syslog we saw something like

Jul 10 17:00:08 hci01 kernel: [21675145.568997] scsi_io_completion_action: 24
callbacks suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.569005] sd 6:0:0:768: [sdau] tag#1298
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.569011] sd 6:0:0:768: [sdau] tag#1298
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.569015] sd 6:0:0:768: [sdau] tag#1298
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.569019] sd 6:0:0:768: [sdau] tag#1298
CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Jul 10 17:00:08 hci01 kernel: [21675145.569021] print_req_error: 24 callbacks
suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.569025] blk_update_request: critical
target error, dev sdau, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio
class 0
Jul 10 17:00:08 hci01 kernel: [21675145.601879] sd 6:0:0:768: [sdau] tag#1299
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.601883] sd 6:0:0:768: [sdau] tag#1299
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.601886] sd 6:0:0:768: [sdau] tag#1299
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.601888] sd 6:0:0:768: [sdau] tag#1299
CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Jul 10 17:00:08 hci01 kernel: [21675145.601891] blk_update_request: critical
target error, dev sdau, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class
0
Jul 10 17:00:08 hci01 kernel: [21675145.604213] buffer_io_error: 22 callbacks
suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.604215] Buffer I/O error on dev sdau,
logical block 0, async page read
Jul 10 17:00:08 hci01 kernel: [21675145.634149] sd 6:0:0:768: [sdau] tag#1300
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.634152] sd 6:0:0:768: [sdau] tag#1300
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.634155] sd 6:0:0:768: [sdau] tag#1300
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.634158] sd 6:0:0:768: [sdau] tag#1300

CDB: Read(10) 28 00 00 00 00 00 00 00 01 00

here, the lun id of 768 does not exist on SAN but when I try to manually delete it, after some seconds it still appears.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#1 lore raw
Quoted 61 lines · On 7/10/22 11:47, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=216232

Bug ID: 216232
Summary: mysterious block devices are shown under /dev folder
Product: SCSI Drivers
Version: 2.5
Kernel Version: 5.4.61
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: QLOGIC QLA2XXX
Assignee: [email protected]
Reporter: [email protected]
Regression: No

we are using linux kernel 5.4.61 and fibre channel card is qlogic's ISP2722-based 16/32Gb adapter card.

the problem is that we are seeing some devices with lun 768 with size of 512B shown under /dev folder. In the syslog we saw something like

Jul 10 17:00:08 hci01 kernel: [21675145.568997] scsi_io_completion_action: 24
callbacks suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.569005] sd 6:0:0:768: [sdau] tag#1298
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.569011] sd 6:0:0:768: [sdau] tag#1298
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.569015] sd 6:0:0:768: [sdau] tag#1298
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.569019] sd 6:0:0:768: [sdau] tag#1298
CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Jul 10 17:00:08 hci01 kernel: [21675145.569021] print_req_error: 24 callbacks
suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.569025] blk_update_request: critical
target error, dev sdau, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio
class 0
Jul 10 17:00:08 hci01 kernel: [21675145.601879] sd 6:0:0:768: [sdau] tag#1299
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.601883] sd 6:0:0:768: [sdau] tag#1299
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.601886] sd 6:0:0:768: [sdau] tag#1299
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.601888] sd 6:0:0:768: [sdau] tag#1299
CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Jul 10 17:00:08 hci01 kernel: [21675145.601891] blk_update_request: critical
target error, dev sdau, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class
0
Jul 10 17:00:08 hci01 kernel: [21675145.604213] buffer_io_error: 22 callbacks
suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.604215] Buffer I/O error on dev sdau,
logical block 0, async page read
Jul 10 17:00:08 hci01 kernel: [21675145.634149] sd 6:0:0:768: [sdau] tag#1300
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.634152] sd 6:0:0:768: [sdau] tag#1300
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.634155] sd 6:0:0:768: [sdau] tag#1300
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.634158] sd 6:0:0:768: [sdau] tag#1300
Quoted 5 lines

CDB: Read(10) 28 00 00 00 00 00 00 00 01 00

here, the lun id of 768 does not exist on SAN but when I try to manually delete it, after some seconds it still appears.

This looks more like a configuration issue on the storage. What is the output of 'lsscsi' on your system?

Cheers,

Hannes

Signature · 4 lines
Dr. Hannes Reinecke		           Kernel Storage Architect
[email protected]			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
#2 lore raw

[Bug 216232] mysterious block devices are shown under /dev folder

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=216232

--- Comment #1 from Hannes Reinecke ([email protected]) ---

Quoted 62 lines · On 7/10/22 11:47, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=216232

Bug ID: 216232
Summary: mysterious block devices are shown under /dev folder
Product: SCSI Drivers
Version: 2.5
Kernel Version: 5.4.61
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: QLOGIC QLA2XXX
Assignee: [email protected]
Reporter: [email protected]
Regression: No

we are using linux kernel 5.4.61 and fibre channel card is qlogic's ISP2722-based 16/32Gb adapter card.

the problem is that we are seeing some devices with lun 768 with size of 512B shown under /dev folder. In the syslog we saw something like

Jul 10 17:00:08 hci01 kernel: [21675145.568997] scsi_io_completion_action: 24
callbacks suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.569005] sd 6:0:0:768: [sdau] tag#1298
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.569011] sd 6:0:0:768: [sdau] tag#1298
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.569015] sd 6:0:0:768: [sdau] tag#1298
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.569019] sd 6:0:0:768: [sdau] tag#1298
CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Jul 10 17:00:08 hci01 kernel: [21675145.569021] print_req_error: 24 callbacks
suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.569025] blk_update_request: critical
target error, dev sdau, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio
class 0
Jul 10 17:00:08 hci01 kernel: [21675145.601879] sd 6:0:0:768: [sdau] tag#1299
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.601883] sd 6:0:0:768: [sdau] tag#1299
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.601886] sd 6:0:0:768: [sdau] tag#1299
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.601888] sd 6:0:0:768: [sdau] tag#1299
CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Jul 10 17:00:08 hci01 kernel: [21675145.601891] blk_update_request: critical
target error, dev sdau, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio
class
0
Jul 10 17:00:08 hci01 kernel: [21675145.604213] buffer_io_error: 22 callbacks
suppressed
Jul 10 17:00:08 hci01 kernel: [21675145.604215] Buffer I/O error on dev sdau,
logical block 0, async page read
Jul 10 17:00:08 hci01 kernel: [21675145.634149] sd 6:0:0:768: [sdau] tag#1300
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 10 17:00:08 hci01 kernel: [21675145.634152] sd 6:0:0:768: [sdau] tag#1300
Sense Key : Illegal Request [current]
Jul 10 17:00:08 hci01 kernel: [21675145.634155] sd 6:0:0:768: [sdau] tag#1300
Add. Sense: Logical block address out of range
Jul 10 17:00:08 hci01 kernel: [21675145.634158] sd 6:0:0:768: [sdau] tag#1300
Quoted 6 lines

CDB: Read(10) 28 00 00 00 00 00 00 00 01 00

here, the lun id of 768 does not exist on SAN but when I try to manually delete
it, after some seconds it still appears.

This looks more like a configuration issue on the storage. What is the output of 'lsscsi' on your system?

Cheers,

Hannes

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#3 lore raw

[Bug 216232] mysterious block devices are shown under /dev folder

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=216232

--- Comment #2 from jshen28 ([email protected]) --- Hi, thank you very much for feedback,

the lsscsi output is quite long so I just pick a small part of it. I put it in the attachment, please have a look. thank you.

Best,
Norman

Quoted 105 lines · On Wed, Jul 13, 2022 at 5:09 PM <[email protected]> wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=216232

--- Comment #1 from Hannes Reinecke ([email protected]) ---

Quoted 18 lines · On 7/10/22 11:47, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=216232

Bug ID: 216232
Summary: mysterious block devices are shown under /dev folder
Product: SCSI Drivers
Version: 2.5
Kernel Version: 5.4.61
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: QLOGIC QLA2XXX
Assignee: [email protected]
Reporter: [email protected]
Regression: No

Quoted 4 lines

we are using linux kernel 5.4.61 and fibre channel card is qlogic's ISP2722-based 16/32Gb adapter card.

the problem is that we are seeing some devices with lun 768 with size of

512B

Quoted 3 lines

shown under /dev folder. In the syslog we saw something like

Jul 10 17:00:08 hci01 kernel: [21675145.568997]

scsi_io_completion_action: 24

Quoted 2 lines

callbacks suppressed

Jul 10 17:00:08 hci01 kernel: [21675145.569005] sd 6:0:0:768: [sdau]

tag#1298

Quoted 2 lines

FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Jul 10 17:00:08 hci01 kernel: [21675145.569011] sd 6:0:0:768: [sdau]

tag#1298

Quoted 2 lines

Sense Key : Illegal Request [current]

Jul 10 17:00:08 hci01 kernel: [21675145.569015] sd 6:0:0:768: [sdau]

tag#1298

Quoted 2 lines

Add. Sense: Logical block address out of range

Jul 10 17:00:08 hci01 kernel: [21675145.569019] sd 6:0:0:768: [sdau]

tag#1298

Quoted 2 lines

CDB: Read(10) 28 00 00 00 00 00 00 00 01 00

Jul 10 17:00:08 hci01 kernel: [21675145.569021] print_req_error: 24

callbacks

Quoted 2 lines

suppressed

Jul 10 17:00:08 hci01 kernel: [21675145.569025] blk_update_request:

critical

Quoted 1 line

target error, dev sdau, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1

prio

Quoted 2 lines

class 0

Jul 10 17:00:08 hci01 kernel: [21675145.601879] sd 6:0:0:768: [sdau]

tag#1299

Quoted 2 lines

FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Jul 10 17:00:08 hci01 kernel: [21675145.601883] sd 6:0:0:768: [sdau]

tag#1299

Quoted 2 lines

Sense Key : Illegal Request [current]

Jul 10 17:00:08 hci01 kernel: [21675145.601886] sd 6:0:0:768: [sdau]

tag#1299

Quoted 2 lines

Add. Sense: Logical block address out of range

Jul 10 17:00:08 hci01 kernel: [21675145.601888] sd 6:0:0:768: [sdau]

tag#1299

Quoted 2 lines

CDB: Read(10) 28 00 00 00 00 00 00 00 01 00

Jul 10 17:00:08 hci01 kernel: [21675145.601891] blk_update_request:

critical

Quoted 4 lines

target error, dev sdau, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class
0

Jul 10 17:00:08 hci01 kernel: [21675145.604213] buffer_io_error: 22

callbacks

Quoted 2 lines

suppressed

Jul 10 17:00:08 hci01 kernel: [21675145.604215] Buffer I/O error on dev

sdau,

Quoted 2 lines

logical block 0, async page read

Jul 10 17:00:08 hci01 kernel: [21675145.634149] sd 6:0:0:768: [sdau]

tag#1300

Quoted 2 lines

FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Jul 10 17:00:08 hci01 kernel: [21675145.634152] sd 6:0:0:768: [sdau]

tag#1300

Quoted 2 lines

Sense Key : Illegal Request [current]

Jul 10 17:00:08 hci01 kernel: [21675145.634155] sd 6:0:0:768: [sdau]

tag#1300

Quoted 2 lines

Add. Sense: Logical block address out of range

Jul 10 17:00:08 hci01 kernel: [21675145.634158] sd 6:0:0:768: [sdau]

tag#1300

Quoted 6 lines

CDB: Read(10) 28 00 00 00 00 00 00 00 01 00

here, the lun id of 768 does not exist on SAN but when I try to manually delete
it, after some seconds it still appears.

This looks more like a configuration issue on the storage. What is the output of 'lsscsi' on your system?

Cheers,

Hannes

--
You may reply to this email to add a comment.

You are receiving this mail because:
You reported the bug.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.