From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 216232] mysterious block devices are shown under /dev folder
Date: Wed, 13 Jul 2022 09:09:07 +0000 [thread overview]
Message-ID: <bug-216232-11613-cxlmA3AD89@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216232-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216232
--- Comment #1 from Hannes Reinecke (hare@suse.de) ---
On 7/10/22 11:47, bugzilla-daemon@kernel.org 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: scsi_drivers-qla2xxx@kernel-bugs.osdl.org
> Reporter: yshxxsjt715@gmail.com
> 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.
>
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 are watching the assignee of the bug.
next prev parent reply other threads:[~2022-07-13 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 9:47 [Bug 216232] New: mysterious block devices are shown under /dev folder bugzilla-daemon
2022-07-13 9:09 ` Hannes Reinecke
2022-07-13 9:09 ` bugzilla-daemon [this message]
2022-07-15 7:08 ` [Bug 216232] " bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216232-11613-cxlmA3AD89@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox