From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bernhard Sulzer <micraft.b@gmail.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: Invalid optimal transfer size 33553920 accepted when physical_block_size 512
Date: Sun, 22 Mar 2020 21:41:27 -0400 [thread overview]
Message-ID: <yq1blonrgoo.fsf@oracle.com> (raw)
In-Reply-To: <4f6eb89d-57e4-a229-2e95-29fe4a691381@gmail.com> (Bernhard Sulzer's message of "Mon, 23 Mar 2020 00:40:39 +0100")
Bernhard,
> There does not seem to be a change in capaticy detected - you got a
> almost complete section of dmesg from me. Anyway, here's the whole
> thing after plugging in:
OK, got a workaround. Will send tomorrow.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-03-23 1:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 14:32 Invalid optimal transfer size 33553920 accepted when physical_block_size 512 Bernhard Sulzer
2020-03-22 15:45 ` Martin K. Petersen
[not found] ` <accd7d25-ee35-11b9-e49b-76e20d9550f2@gmail.com>
[not found] ` <yq1pnd4uxof.fsf@oracle.com>
2020-03-22 17:41 ` Bernhard Sulzer
[not found] ` <yq1pnd4tbxm.fsf@oracle.com>
2020-03-22 19:45 ` Bernhard Sulzer
2020-03-22 21:06 ` Martin K. Petersen
2020-03-22 21:20 ` Bernhard Sulzer
2020-03-22 21:53 ` Bernhard Sulzer
2020-03-22 22:45 ` Martin K. Petersen
2020-03-22 23:10 ` Bernhard Sulzer
2020-03-22 23:22 ` Bernhard Sulzer
2020-03-22 23:32 ` Martin K. Petersen
2020-03-22 23:40 ` Bernhard Sulzer
2020-03-23 1:41 ` Martin K. Petersen [this message]
2020-03-24 13:49 ` Bryan Gurney
2020-03-24 15:47 ` [PATCH] scsi: sd: Fix optimal I/O size for devices that change reported values Martin K. Petersen
2020-03-24 15:52 ` Invalid optimal transfer size 33553920 accepted when physical_block_size 512 Martin K. Petersen
2020-03-24 16:14 ` Bernhard Sulzer
2020-03-27 0:54 ` Martin K. Petersen
2020-03-22 20:57 ` [PATCH] scsi: sd: Optimal I/O size should be a multiple of reported granularity 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=yq1blonrgoo.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=micraft.b@gmail.com \
/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