From: Hussam Al-Tayeb <ht990332@gmx.com>
To: linux-kernel@vger.kernel.org
Subject: Debug scsi message in linux 4.19.31
Date: Sun, 24 Mar 2019 15:07:21 +0200 [thread overview]
Message-ID: <624bbdbb24ad7db69be29956cbf14689fd003cdb.camel@gmx.com> (raw)
Hi. I'm seeing a debug message in linux stable kernel 4.19.31 with this
patch
scsi-sd-optimal-i-o-size-should-be-a-multiple-of-physical-block-
size.patch
I am getting:
Mar 23 17:40:10 hades kernel: sd 0:0:0:0: [sda] Optimal transfer size 0
bytes < PAGE_SIZE (4096 bytes)
Mar 23 17:40:10 hades kernel: sd 2:0:0:0: [sdb] Optimal transfer size 0
bytes < PAGE_SIZE (4096 bytes)
Mar 23 17:46:43 hades kernel: sd 4:0:0:0: [sdc] Optimal transfer size 0
bytes < PAGE_SIZE (4096 bytes)
sda and sdb are physically attached SATA mechanical disks (Western
Digital and Seagate, respectively).
sdc is a kingston usb flash drive. All three disks use ext4 luks
encrypted partitions.
Is the fact that it is reporting 0 as optimal transfer size something I
should worry about? Note that the the three storage devices are from
three different manufacturers.
This particular machine is a Lenovo Intel(R) Core(TM) i5-6400 CPU @
2.70GHz with 16GB Kingston DDR4 ram.
I tried moving the root disk to another machine (a DELL Core I7 7700
with slightly faster ram from Samsung) and I saw the same message.
This seems like a patch that fits better in a hardware vendor or
operating system distributor tree than the upstream kernel. Shouldn't
stable tree kernels only contain direct fixes and regression fixes?
Does it really belong in an LTS kernel?
Please CC me in your reply as I am not subscribed to the list.
Thank you.
next reply other threads:[~2019-03-24 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 13:07 Hussam Al-Tayeb [this message]
2019-03-24 16:18 ` Randy Dunlap
2019-03-25 0:04 ` Martin K. Petersen
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=624bbdbb24ad7db69be29956cbf14689fd003cdb.camel@gmx.com \
--to=ht990332@gmx.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®