HiI've also been thinking about a Pi 5 with dual m.2 hat. It seems the contenders are the Pimironi dual base and the Geekworm dual 2280 NVMe SSD shield.Bought a Pi5 with dual nvme hat.
I went to setup boot from nvme - somebody suggested to use zfs
had a bit of a look into it and was thinking what I want I think is
2 x pi5 with dual nvme hat with 2 x nvme drives - so pi5-a and pi5-b
then I can setup a vdev with 1 local disk and 1 attached disk in a mirror setup
so on pi5-a I can use nvme1.1 + iscsi from pi5-b
pi5-a nvme1.2 I can server up via iscsi to pi5-b
and
on pi5-b I can use nvme1.1 + iscsi from pi5-a
pi5-b nvme1.2 I can server up via iscsi to pi5-a
This way I can lose a nvme and also a whole pi5 .. lets say my dog eats pi5-a I still have a copy (mirror) of the zfs on pi5-b
Then as my final bit of backup wizardry I can sync up via google drive !
I've been in the corporate world too long haven't played with the new fun stuff in a while.(ZFS), I have done iscsi servers
https://shop.pimoroni.com/products/nvme ... 4434895955
https://geekworm.com/products/x1004
My suspicion is some SSDs will take too much power when operated in pairs and simply not work. In particular, I'm not sure whether there are any 4TB drives that can be paired.
ZFS was included in Sun Solaris around 2001. BTRFS is still somewhat experimental but I felt it was good enough around kernel 3.14 in 2014. Since both ZFS and BTRFS have send and receive functionality that allows one to replicate disk pools in physically different locations, the way I'd set things up would be as follows:For more information, see
- Pi 5-a has a two SSD ZFS (or BTRFS) drive pool with mirrored redundancy between drives.
- Pi 5-b has a replicated copy of the drive pool created using send and receive.
https://openzfs.org/wiki/Documentation/ZfsSend
https://btrfs.readthedocs.io/en/latest/ ... ceive.html
Note that the only purpose of Pi 5-b is to keep a copy of the replicated pool. All other activity is with the Pi 5-a. Note also this is a high-availability configuration and backups still need to be considered separately.
If one SSD on the Pi 5-a fails, replace it and rebalance to restore the mirrored redundancy. If the dog eats the Pi 5-a (that's also a problem around here), then fail over to the Pi 5-b and take the dog to the veterinarian (possibly in reverse order).
I think for me this is more of a learning thing so I have 2x 500Gb nvme installed on my current - i bought a new pi5 with the dual from Pimironi , didn't see the other one.
In my head it was making pi5-a & pi5-b highly available.
So currently i have internal zone files for bind on 1 mini pc and then setup slaves on the other 2 dns resolvers. pain if I lose the main mini.
Next thought was shared filesystem with puppet files to configure things. this could be google drive - or git. that way i can have 3 master zones know they will always be in sync.
Then I can build other things like that. want to build a new media server ... but that will probably not happen - just want to play with the resilient / backup / zfs and pi5 & nvme
Statistics: Posted by KeyzerSuze — Fri Jun 14, 2024 4:49 am