From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: new drive is 4 sectors shorter, can it be used for swraid5 array?
Date: Sat, 19 Mar 2022 15:45:59 +0500 [thread overview]
Message-ID: <20220319154559.09f649e4@nvm> (raw)
In-Reply-To: <20220318173007.3ad9348c@nvm>
On Fri, 18 Mar 2022 17:30:07 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> However there should not be such size difference in the first place
If we look closely though, there actually doesn't appear to be:
> On Thu, 17 Mar 2022 20:08:55 -0700
> Marc MERLIN <marc@merlins.org> wrote:
>
> > old drive:
> > User Capacity: 6,001,175,126,016 bytes [6.00 TB]
> >
> > new drive:
> > User Capacity: 6,001,175,126,016 bytes [6.00 TB]
As for...
> > 8 128 5860522584 sdi
> > 8 129 5860521543 sdi1
> >
> > 8 160 5860522580 sdk
> > 8 161 5860521536 sdk1
Which tool returns this output?
What do you get for
blockdev --getsize64 /dev/sdi
blockdev --getsize64 /dev/sdk
If this returns the same size for both, wipe a few first MB the new drive with
zeroes using dd, and try a different partitioning tool.
--
With respect,
Roman
next prev parent reply other threads:[~2022-03-19 10:46 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 [this message]
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=20220319154559.09f649e4@nvm \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--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).