From: Wolf Noble <wolf@wolfspyre.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] rebuilding a cluster node (new root disks (ext4 -> zfs))
Date: Fri, 15 Apr 2022 14:09:31 -0500 [thread overview]
Message-ID: <22DAD9B6-4EFE-48EA-A636-F84CE858B5D0@wolfspyre.com> (raw)
Howdy all!
1) i hope you are doing well, and feel appreciated and respected.
2) Im rebuilding my cluster nodes one at a time.
i was hoping there is a guide someplace that enumerated the files on (original root disks) that should be copied over ‘new’ files to allow the newly rebuilt node to join the cluster with ease.
i have a hacky, ugly way, but i’m hoping there’s something a bit more canonical than just my trial and error.
I’ll happily contribute my ‘moving root to zfs’ notes to that doc… if someone could be so kind as to point me in the direction of a clue. :)
TIA!
🐺W
[= The contents of this message have been written, read, processed, erased, sorted, sniffed, compressed, rewritten, misspelled, overcompensated, lost, found, and most importantly delivered entirely with recycled electrons =]
reply other threads:[~2022-04-15 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22DAD9B6-4EFE-48EA-A636-F84CE858B5D0@wolfspyre.com \
--to=wolf@wolfspyre.com \
--cc=pve-user@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox