From: Phillip Susi <phill@thesusis.net>
To: Stefanie Leisestreichler <stefanie.leisestreichler@peter-speer.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Setup Recommendation on UEFI/GRUB/RAID1/LVM
Date: Tue, 14 Apr 2020 14:14:21 -0400 [thread overview]
Message-ID: <875ze23pfm.fsf@vps.thesusis.net> (raw)
In-Reply-To: <fc12df3c-aac9-4aa8-a596-f13225161e22@peter-speer.de>
Stefanie Leisestreichler writes:
> To be safe on system updates I want to use LVM snapshots. I like to make
> a LVM-based snapshot when the system comes up, do the system updates,
> perform the test and dicide either to go with the updates made or revert
> to the original state.
Tradditional LVM snapshots were not suitable for keeping multiple, long
lived snapshots around. They were really only for temporary use, such
as taking a snapshot to do a dump of without having to shut down
services. I seem to remember they were developing a new multi snapshot
dm backend that would address some of these shortcomings, but I can't
find anything about that now in the google machine.
> I have read that - when using UEFI - the EFI-System-Partition (ESP) has
> to reside in a own native partition, not in a RAID nor LVM block device.
Correct.
> I wonder, how I should build up this construct. I thought I could build
> one partition with TOTAL_SIZE - 100M, Type FD00, on each device, take
> these two (sda1 + sdb1) and build a RAID 1 array named md0. Next make
> md0 the physical volume of my LVM (pvcreate /dev/md0) and after that add
> a volume group in which I put my logical volumes:
> - swap - type EF00
EF00 is a GPT partition type. Since this is a logical volume rather
than a GPT partition, there is no EF00.
> - /boot - with filesystem fat32 for uefi
Like you mentioned above, this needs to be a native partition, not a
logical volume. Actually you only need /boot/EFI in a native fat32
partition, not all of /boot.
next prev parent reply other threads:[~2020-04-14 18:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:02 Setup Recommendation on UEFI/GRUB/RAID1/LVM Stefanie Leisestreichler
2020-04-14 14:20 ` Wols Lists
2020-04-14 14:27 ` Reindl Harald
2020-04-14 15:12 ` Stefanie Leisestreichler
2020-04-14 17:35 ` Wols Lists
2020-04-14 19:13 ` Stefanie Leisestreichler
2020-04-14 19:36 ` Wols Lists
2020-04-17 23:06 ` Nix
2020-04-20 9:23 ` Stefanie Leisestreichler
2020-04-20 9:45 ` Stefanie Leisestreichler
2020-04-20 11:05 ` Nix
2020-04-20 12:01 ` Stefanie Leisestreichler
2020-04-16 1:50 ` David C. Rankin
2020-04-16 11:16 ` Wols Lists
2020-04-16 1:58 ` David C. Rankin
2020-04-14 16:00 ` G
2020-04-14 16:14 ` Stefanie Leisestreichler
2020-04-17 23:10 ` Nix
2020-04-24 19:15 ` Phillip Susi
2020-04-24 20:24 ` Nix
2020-04-14 16:20 ` Reindl Harald
2020-04-14 16:41 ` Stefanie Leisestreichler
2020-04-16 17:00 ` G
2020-04-14 18:14 ` Phillip Susi [this message]
2020-04-14 19:00 ` Stefanie Leisestreichler
2020-04-14 20:05 ` antlists
2020-04-17 23:24 ` Nix
[not found] ` <394a3255-251c-41d1-8a65-2451e5503ef9@teksavvy.com>
2020-04-15 15:53 ` Stefanie Leisestreichler
2020-04-15 16:10 ` Stefanie Leisestreichler
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=875ze23pfm.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=linux-raid@vger.kernel.org \
--cc=stefanie.leisestreichler@peter-speer.de \
/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).