linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Dimitri John Ledkov <xnox@debian.org>, stan@hardwarefreak.com
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Why 4k native drives haven't arrived
Date: Wed, 22 Jan 2014 21:19:34 -0500	[thread overview]
Message-ID: <52E07C36.5080109@ubuntu.com> (raw)
In-Reply-To: <CANBHLUjceX=NOqwdWWSGS3w=GrJaVt1OvH0PMrgQ5Ce30O+Smg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/03/2014 06:27 AM, Dimitri John Ledkov wrote:
> And even if one would buy a 4k native drive, i would have thought 
> there'd be other obstacles in trying it out e.g. not having a SATA 
> port =) considering it was created two years after Windows XP =)
> or since a 4k native drive is likely to be 2TB+ in size, GPT
> support is required to address the whole drive...

Actually, 4k native drives can use MBR up to 16 TB.  The limitation on
the MBR partition table is 32 bits to address sectors, so larger
sectors => higher addressable size.  Some of the fakeraid controllers
on the market take advantage of this fact and report a 1k or 2k
physical sector size to allow MBR partitioning on larger arrays.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJS4Hw2AAoJEI5FoCIzSKrwX5YH/joOvhkO9wHpZOgbCfPhTvzC
Zax4nNuv9m0jAHzx+D0jqWzq/maf6ju0Xu3Sc49Iyy1ZfCeNXe64KrLnXyF2He9W
TMMqDoAe0pIqdSxMtLr/1G/kJa1pxIcaoYvtc2val3MPxz/dw32XFk60fyBBSGYC
n5f2Hs1TB4H0uo1gE4ywtN+fLtAQoqhZpHYIb0rS26zdwMJ3ho3qKwJeONy4FkhQ
pKh4TTJBBMKe/Iz4v4+5RP+yq3Jlx860c+CMHq8amtGHPiBmGBL4WpE6lul/MHGn
WBBv0g/VNd5M7K9Q/g01sIIRwyFisEImMmvamC9ctsUlcFzMEtkRfRyM1C+2SfU=
=bHlp
-----END PGP SIGNATURE-----

  reply	other threads:[~2014-01-23  2:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  1:53 Why 4k native drives haven't arrived Stan Hoeppner
2014-01-03 11:23 ` Mikael Abrahamsson
2014-01-03 11:27 ` Dimitri John Ledkov
2014-01-23  2:19   ` Phillip Susi [this message]
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=52E07C36.5080109@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=stan@hardwarefreak.com \
    --cc=xnox@debian.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).