linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Why 4k native drives haven't arrived
Date: Thu, 02 Jan 2014 19:53:11 -0600	[thread overview]
Message-ID: <52C61807.6050906@hardwarefreak.com> (raw)

Until someone demonstrates otherwise I will continue to state that 4K
native drives are still not on the open market.  And the reason for this
is quite logical if given a moment of thought.

Advanced Format 512e drives, drives with 4K native sectors but 512B
sectors presented to the host, fully accomplished the goal of the
spinning disk drive manufacturers.  That goal was simply to pack more
data per platter, on average about 11% more, by reducing the amount of
bits consumed for ECC.  I.e. they can sell a lager capacity drive using
the same hardware as a native 512 byte/sector drive, or with some drive
capacities, reduce the number of platters while maintaining the same
capacity, thus reducing component and production cost, and hopefully
retail price.

The physical sector size presented to the host is irrelevant to the
drive manufacturers, given the singular goal above.  Switching to a
native 4K sector does not benefit the manufacturers.  At the current
time it actually will cause them tremendous problems.

If they were to put 4K native drives on the market today, many millions
of Windows XP users would buy the drives, ignoring, or simply not
reading far enough to find the "4K native" warnings.  They then return
the drives when they don't work, causing great ill will, bad reviews
tarnishing manufacturers' reputations, and decreasing repeat business.
Thus native 4K drives will not be on the open market until the
manufacturers are comfortable that most legacy machines have been
retired, eliminating the possibility of the scenario above.

The first units of native 4K drives will be, or possibly already have
been, to OEMs who exercise control over which systems and disk arrays in
which the drives will be installed.  This prevents such a problem in the
enterprise space, as purchasers typically rely on their vendors to do
compatibility matching.  Enterprise OEMs have long maintained such
product compatibility databases.

-- 
Stan



             reply	other threads:[~2014-01-03  1:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  1:53 Stan Hoeppner [this message]
2014-01-03 11:23 ` Why 4k native drives haven't arrived Mikael Abrahamsson
2014-01-03 11:27 ` Dimitri John Ledkov
2014-01-23  2:19   ` Phillip Susi
2014-01-03 21:04 ` Martin K. Petersen
2014-01-04 18:40   ` Stan Hoeppner
2014-01-06 23:35     ` Martin K. Petersen
2014-01-05 18:48   ` Peter Grandi
2014-01-06 23:50     ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2014-01-09 21:49 Chris Murphy
2014-01-12  4:01 ` Chris Murphy
2014-01-12 13:55   ` Martin K. Petersen
     [not found]     ` <F92ECEC1-D375-498B-8C6A-C88C815C325F@colorremedies.com>
2014-01-12 18:32       ` Martin K. Petersen
2014-01-12 19:04         ` Chris Murphy
2014-01-12 19:27           ` Chris Murphy
2014-01-12 20:25           ` Roman Mamedov
2014-01-12 18:41     ` Stan Hoeppner

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=52C61807.6050906@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).