From: Marc MERLIN <marc@merlins.org>
To: linux-raid@vger.kernel.org
Subject: new drive is 4 sectors shorter, can it be used for swraid5 array?
Date: Thu, 17 Mar 2022 20:08:55 -0700 [thread overview]
Message-ID: <20220318030855.GV3131742@merlins.org> (raw)
old drive:
Device Model: ST6000VN0041-2EL11C
Serial Number: ZA18WX4T
LU WWN Device Id: 5 000c50 0a47d527a
Firmware Version: SC61
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
8 128 5860522584 sdi
8 129 5860521543 sdi1
new drive:
Device Model: ST6000VN001-2BB186
Serial Number: ZR118A1Y
LU WWN Device Id: 5 000c50 0dba1b3c0
Firmware Version: SC60
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
8 160 5860522580 sdk
8 161 5860521536 sdk1
New drive is 4 sectors shorter, so I assume I can't use it as a replacement in my md5
array because it's 4 sectors too short, or does swraid5 not need the last few sectors
of a drive?
Looks like formatting as MDR won't help, I'm still 4 sectors short.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next reply other threads:[~2022-03-18 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 3:08 Marc MERLIN [this message]
2022-03-18 7:54 ` new drive is 4 sectors shorter, can it be used for swraid5 array? 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
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=20220318030855.GV3131742@merlins.org \
--to=marc@merlins.org \
--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 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.