From: Mike Snitzer <snitzer@redhat.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: John Dorminy <jdorminy@redhat.com>,
Joe Shimkus <jshimkus@redhat.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"tjaskiew@redhat.com" <tjaskiew@redhat.com>,
John Pittman <jpittman@redhat.com>,
Alasdair G Kergon <agk@redhat.com>,
Bryan Gurney <bgurney@redhat.com>
Subject: SMR 512e drive firmware advertising misleading limits? [was: Re: [RFC PATCH 1/1] dm: add dust target]
Date: Wed, 9 Jan 2019 09:29:13 -0500 [thread overview]
Message-ID: <20190109142913.GA26563@redhat.com> (raw)
In-Reply-To: <BYAPR04MB581645C55BCC328E193D3DBEE78B0@BYAPR04MB5816.namprd04.prod.outlook.com>
On Tue, Jan 08 2019 at 8:03pm -0500,
Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
> You may want to check against the physical_block_size, and not the logical. SMR
> disks that are 512 e (512B logical and 4K physical) can handle reads in 512B
> units but writes have to be 4K. These are exceptions though and kind of breaking
> all LBA definitions known to men... This check on the physical_block_size can be
> limited to setups where the underlying disk is SMR.
Damien, this sounds like a serious issue with SMR firmware. If the
512e SMR drive cannot handle 512b writes then it has no business
advertising 512B logical. It should be advertising 4K logical.
What am I missing?
Mike
next prev parent reply other threads:[~2019-01-09 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:31 [RFC PATCH 0/1] dm: add dm-dust, a bad sector emulator Bryan Gurney
2019-01-07 19:31 ` [RFC PATCH 1/1] dm: add dust target Bryan Gurney
2019-01-08 0:10 ` Benjamin Marzinski
2019-01-08 15:30 ` Bryan Gurney
2019-01-08 16:23 ` Mike Snitzer
2019-01-08 19:52 ` Bryan Gurney
2019-01-08 20:29 ` Mike Snitzer
2019-01-09 1:03 ` Damien Le Moal
2019-01-09 14:29 ` Mike Snitzer [this message]
2019-01-10 4:58 ` SMR 512e drive firmware advertising misleading limits? [was: Re: [RFC PATCH 1/1] dm: add dust target] Damien Le Moal
2019-01-08 17:36 ` [RFC PATCH 1/1] dm: add dust target Benjamin Marzinski
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=20190109142913.GA26563@redhat.com \
--to=snitzer@redhat.com \
--cc=Damien.LeMoal@wdc.com \
--cc=agk@redhat.com \
--cc=bgurney@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jdorminy@redhat.com \
--cc=jpittman@redhat.com \
--cc=jshimkus@redhat.com \
--cc=tjaskiew@redhat.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 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.