From: Stan Hoeppner <stan@hardwarefreak.com>
To: Joe Landman <joe.landman@gmail.com>,
Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
Cc: Phillip Susi <psusi@ubuntu.com>,
joystick <joystick@shiftmail.org>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: The chunk size paradox
Date: Thu, 02 Jan 2014 22:24:38 -0600 [thread overview]
Message-ID: <52C63B86.3050501@hardwarefreak.com> (raw)
In-Reply-To: <52C62C5B.7080006@hardwarefreak.com>
On 1/2/2014 9:19 PM, Stan Hoeppner wrote:
> On 1/2/2014 9:14 PM, Joe Landman wrote:
>
>> But they are 4k native and you can use them that way. The 512 byte
>> layer is emulated.
>
> Which series is this? Is the mode switched via a jumper?
According to WD's web site, all of their "datacenter" drives are 512n or
512e, none are listed as native 4K. Same for their consumer drives.
I have just located about a dozen Seagate enterprise SSHD and Savio 15K
models that are offered in native 4K. These must be relatively new. I
find no 4Kn high cap Seagate drives.
All of the HGST enterprise drives are 512n/512e, select few support 520/528.
Toshiba's drive spec sheets don't even list sector size...
--
Stan
next prev parent reply other threads:[~2014-01-03 4:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 18:48 The chunk size paradox Phillip Susi
2013-12-30 23:38 ` Peter Grandi
2013-12-31 0:01 ` Wolfgang Denk
2013-12-31 13:51 ` David Brown
2014-01-02 20:08 ` Phillip Susi
2014-01-02 14:49 ` joystick
2014-01-02 15:24 ` Phillip Susi
2014-01-02 15:41 ` Stan Hoeppner
2014-01-02 16:31 ` Phillip Susi
2014-01-02 18:02 ` Stan Hoeppner
2014-01-02 19:10 ` Phillip Susi
2014-01-02 22:49 ` Peter Grandi
2014-01-02 23:16 ` Stan Hoeppner
2014-01-03 1:02 ` Phillip Susi
2014-01-02 19:21 ` Joe Landman
2014-01-02 22:42 ` Stan Hoeppner
2014-01-02 22:56 ` Carsten Aulbert
2014-01-03 0:19 ` Phillip Susi
2014-01-03 1:24 ` Stan Hoeppner
2014-01-03 3:14 ` Joe Landman
2014-01-03 3:19 ` Stan Hoeppner
2014-01-03 4:24 ` Stan Hoeppner [this message]
2014-01-02 23:22 ` Peter Grandi
2014-01-03 3:09 ` Joe Landman
2014-01-03 4:58 ` Joe Landman
2014-01-02 22:32 ` Wolfgang Denk
2014-01-03 14:51 ` Benjamin ESTRABAUD
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=52C63B86.3050501@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=Carsten.Aulbert@aei.mpg.de \
--cc=joe.landman@gmail.com \
--cc=joystick@shiftmail.org \
--cc=linux-raid@vger.kernel.org \
--cc=psusi@ubuntu.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;
as well as URLs for NNTP newsgroup(s).