From: Steven Lembark <lembark@wrkhors.com>
To: gentoo-user@lists.gentoo.org
Cc: lembark@wrkhors.com
Subject: Re: [gentoo-user] Fun with mdadm (Software RAID)
Date: Wed, 25 Dec 2024 16:16:50 -0500 [thread overview]
Message-ID: <20241225161650.5641a98a.lembark@wrkhors.com> (raw)
In-Reply-To: <Z2hxBStiVi-BC5GH@MAC.fritz.box>
> I think any system admins reading this would long for the
> predictability of "consumer hardware", having too often been
> confronted with indistinguishable 32 hex digit identifiers. I would
> imagine it quite likely that the said admins have written scripts to
> make this more manageable.
Simple fix: use LVM, let it deal with the UUID. At that point
the PV's get UUID's, the VG's get UUID's, the LV's get UUID's
and you never have to type or see or use them.
Snippet from my /etc/fstab:
/dev/vg00/root / xfs ...
/dev/vg00/var /var xfs ...
/dev/vg00/var-tmp /var/tmp xfs ...
this is basically the same fstab on my server & notebook, hasn't
changed in the transitions from ATA to SATA to SCSI to SAS to
NVME.
If you want mirroring then either create a mirror with mdadm
and use it as a PV -- kenel will auto-start the mirror, vgscan
will find it, and Viola!, it's up -- or use -m2 and mirror/stripe/
RAID5/whatever using lvcreate to spread the data across whatever
you like.
Here I have two nvme's (used to be scsi, then sas) which are mirrored
for vg00 w/ the root, var, home filesystems another that's striped
for /var/tmp and other scratch spaces.
This gives an overview:
https://speakerdeck.com/lembark/its-only-logical-lvm-for-linux
--
Steven Lembark
Workhorse Computing
lembark@wrkhors.com
+1 888 359 3508
prev parent reply other threads:[~2024-12-25 21:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 10:47 [gentoo-user] Fun with mdadm (Software RAID) Alan Mackenzie
2024-12-20 14:50 ` karl
2024-12-20 15:28 ` Alan Mackenzie
2024-12-20 17:44 ` karl
2024-12-20 20:19 ` Alan Mackenzie
2024-12-20 20:38 ` Hoël Bézier
2024-12-20 20:53 ` Alan Mackenzie
2024-12-20 22:02 ` karl
2024-12-30 4:08 ` Frank Steinmetzger
2024-12-20 22:02 ` karl
2024-12-21 12:43 ` Alan Mackenzie
2024-12-21 16:36 ` Alan Mackenzie
2024-12-21 16:45 ` karl
2024-12-21 16:58 ` Alan Mackenzie
2024-12-22 13:08 ` Alan Mackenzie
2024-12-22 12:16 ` Wols Lists
2024-12-22 12:08 ` Wols Lists
2024-12-22 12:02 ` Wols Lists
2024-12-22 13:43 ` Alan Mackenzie
2024-12-22 15:29 ` Peter Humphrey
2024-12-22 16:53 ` Wols Lists
2024-12-22 20:05 ` Alan Mackenzie
2024-12-25 21:16 ` Steven Lembark [this message]
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=20241225161650.5641a98a.lembark@wrkhors.com \
--to=lembark@wrkhors.com \
--cc=gentoo-user@lists.gentoo.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