From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Marc MERLIN <marc@merlins.org>, Roman Mamedov <rm@romanrm.net>,
Roger Heflin <rogerheflin@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: new drive is 4 sectors shorter, can it be used for swraid5 array?
Date: Mon, 21 Mar 2022 19:35:00 +0000 [thread overview]
Message-ID: <87zgljcd5n.fsf@esperi.org.uk> (raw)
In-Reply-To: <01d2c8c5-46ea-f69e-e285-da0abe6cd594@youngman.org.uk> (Wols Lists's message of "Sat, 19 Mar 2022 10:14:16 +0000")
On 19 Mar 2022, Wols Lists uttered the following:
> On 19/03/2022 04:10, Marc MERLIN wrote:
>>> If you find it needs more than the size of sdk1, as an emergency measure you
>>> could wipe off the partition table and add the entire sdk as the array member.
>
>> Yeah, I thought of that, just don't really like it, and not sure if
>> mdadm -can looks for raw drives in addition to partitions
>>
> mdadm has absolutely no trouble with that at all. All it cares about is if something is a block device - if it finds an mdadm
> signature at the start of a block device it will use it.
>
> The problem is the eejits out there who assume that all physical
> drives must be partitioned. And we know from experience that there are
> eejits out there who assume that any drive without an MBR or GPT just
> *must* be unused and it's *perfectly* *okay* to write said MBR or GPT
> *without* *asking*. Just trashing your mdadm (or lvm, or whatever yada
> ydad) signature in the process.
... and we know that some of the eejits out there write EFI firmware :(
and some of them blow away things like this on boot, on resume from
suspend,
> It's not common
... thank goodness.
--
NULL && (void)
next prev parent reply other threads:[~2022-03-21 20:25 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 [this message]
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=87zgljcd5n.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=marc@merlins.org \
--cc=rm@romanrm.net \
--cc=rogerheflin@gmail.com \
/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.