From: Wols Lists <antlists@youngman.org.uk>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>,
David T-G <davidtg-robot@justpickone.org>,
linux-raid@vger.kernel.org
Subject: Re: mirroring existing boot drive sanity check
Date: Fri, 12 Aug 2022 08:23:59 +0100 [thread overview]
Message-ID: <fc6cd184-5570-3afa-e477-03008be58183@youngman.org.uk> (raw)
In-Reply-To: <014ce113-3c6d-ea1d-a576-cb06e5126748@plouf.fr.eu.org>
On 11/08/2022 22:26, Pascal Hambourg wrote:
> However I do not think it is possible to cleanly boot from an
> unpartitioned drive used as a software RAID member, as a RAID capable
> boot loader could hardly fit in the 4-KiB area before the RAID
> superblock. So you still have to create a partition table on the raw
> drives. Also, if you use GPT format and GRUB boot loader, you need to
> create a small (100 kB to 1 MB) partition with type "BIOS boot" (or
> libparted bios_grub flag).
Firstly, is there a 4K block there? iirc it's only 1.2 that leaves said
block.
And secondly, does raid assume that 4K space belongs to it? I know it's
seen as a safety space, so there's nothing permanent left there, but
that's no guarantee raid doesn't think "that's mine, I'll stash
something there temporarily". After all, the space allocated explicitly
begins at the start of the 4K.
(That's completely different to the rouge tools the space is there to
protect - those tools that think "that's nobody's, I'll just grab it".)
Cheers,
Wol
next prev parent reply other threads:[~2022-08-12 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 14:50 mirroring existing boot drive sanity check David T-G
2022-08-10 7:03 ` Wols Lists
2022-08-11 21:26 ` Pascal Hambourg
2022-08-12 7:23 ` Wols Lists [this message]
2022-08-12 8:38 ` Pascal Hambourg
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=fc6cd184-5570-3afa-e477-03008be58183@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=davidtg-robot@justpickone.org \
--cc=linux-raid@vger.kernel.org \
--cc=pascal@plouf.fr.eu.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