From: d tbsky <tbskyd@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Marc MERLIN <marc@merlins.org>,
list Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: new drive is 4 sectors shorter, can it be used for swraid5 array?
Date: Tue, 29 Mar 2022 09:55:40 +0800 [thread overview]
Message-ID: <CAC6SzHL9Vy2Tz_rVFRphTuAjwPNXg59WAuY8JCXXQ94W09y4sw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQyqG_zWhRVXjnc3Prc+J-7hK1hyp28mwyuKWWPJ8Uo5A@mail.gmail.com>
Chris Murphy <lists@colorremedies.com>
> None of my SATA-USB enclosures behave this way. But what it does do is
> mask (lie) the true physical sector size, claiming it's 512 bytes
> instead of 4096 bytes.
normal sata-usb should be ok. seagate/toshiba sata-usb will eat
sectors. some gigabyte dual-bios motherboards will eat sectors (with
disk HPA function).
In the early days different vendors made different capacity harddisks.
But at some moment, maybe 250GB or 500GB, suddenly every vendor made
the same capacity harddisks. It's a mystery to me. who decides the
disk sector numbers? why 2TB disk capacity is not double 1TB, 8TB not
double 4TB? capacity is different for sd-card and ssd, but harddisk
capacity seems normalized at some time.
next prev parent reply other threads:[~2022-03-29 1:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 3:08 new drive is 4 sectors shorter, can it be used for swraid5 array? Marc MERLIN
2022-03-18 7:54 ` Wols Lists
2022-03-18 12:30 ` Roman Mamedov
2022-03-19 4:10 ` Marc MERLIN
2022-03-19 10:14 ` Wols Lists
2022-03-19 22:02 ` Marc MERLIN
2022-03-21 19:35 ` Nix
2022-03-19 10:45 ` Roman Mamedov
2022-03-26 18:01 ` Tom Mitchell
2022-03-26 18:29 ` Wols Lists
2022-03-27 8:40 ` d tbsky
2022-03-28 2:05 ` Marc MERLIN
2022-03-29 0:13 ` Chris Murphy
2022-03-29 1:55 ` d tbsky [this message]
2022-03-30 2:33 ` Andy Smith
2022-04-02 12:48 ` d tbsky
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=CAC6SzHL9Vy2Tz_rVFRphTuAjwPNXg59WAuY8JCXXQ94W09y4sw@mail.gmail.com \
--to=tbskyd@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=marc@merlins.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).