From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: "'Martin K. Petersen'" <martin.petersen@oracle.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: 5.2.x kernel: WD 8TB USB Drives: Unaligned partial completion (resid=78, sector_sz=512)
Date: Mon, 12 Aug 2019 22:12:42 -0400 [thread overview]
Message-ID: <yq1r25p7qzp.fsf@oracle.com> (raw)
In-Reply-To: <002d01d54dc3$17c278c0$47476a40$@lucidpixels.com> (Justin Piszcz's message of "Thu, 8 Aug 2019 04:27:18 -0400")
Justin,
>> Attached 2 x brand new Western Digital 8TB USB 3.0 drives awhile back
>> and ran some file copy tests and was getting these warnings-- is
>> there any way to avoid these warnings? I did confirm with parted
>> that the partition was aligned but this appears to be something
>> related to the firmware on the device according to [1] and [2]?
> sg_vpd_bdc.txt
> Block device characteristics VPD page (SBC):
> Nominal rotation rate: 5400 rpm
> Product type: Not specified
> WABEREQ=0
> WACEREQ=0
> Nominal form factor: 3.5 inch
> ZONED=0
Damien: What can we do to limit the messages in cases like this? Would
it make sense to make the residual warning conditional on sd_is_zoned()?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-08-13 2:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 9:10 5.2.x kernel: WD 8TB USB Drives: Unaligned partial completion (resid=78, sector_sz=512) Justin Piszcz
2019-08-03 9:10 ` Justin Piszcz
2019-08-03 11:36 ` Markus Reichelt
2019-08-03 19:00 ` Alan Stern
2019-08-03 19:00 ` Alan Stern
2019-08-03 19:37 ` Justin Piszcz
2019-08-03 19:37 ` Justin Piszcz
2019-08-08 2:03 ` Martin K. Petersen
2019-08-08 2:03 ` Martin K. Petersen
2019-08-08 8:27 ` Justin Piszcz
2019-08-08 8:27 ` Justin Piszcz
2019-08-13 2:12 ` Martin K. Petersen [this message]
2019-08-13 3:47 ` Damien Le Moal
2019-08-13 10:48 ` Damien Le Moal
2019-08-13 20:58 ` Justin Piszcz
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=yq1r25p7qzp.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Damien.LeMoal@wdc.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.