@1fallen
This is kind of a sidebar but now as it will dealing with expanding a existing pool or array depending upon one’s understanding of ZFS. It is relevant to the discussion of backups.
Specifically the attach command, which I ran across on several sites. Which is supposed to allow one to increase the pool width (drive #'s ) in a raidz / mirrors. Excited I decided to try this feature which failed miserably. So more searching digging through the Doc’s and online manuals. Only to find out the documentors have out run the Dev’s on the release. Which explains why I ran into failures.
While currently the feature is supported in the current releases of ZFS in mirrors and other uses except for raidz configurations ( i.e z1, z2, z3) . But is supposed to be supported across the board with ZFS ver 2.3 . Which will be a boon to those with hardware limitations or budgets.
But will have a slight penalty in drive space efficiency vs just assembling the desired number of drive width when initially creating the pool. Looks to be in my understanding a worthy upgrade, that closes the gap on the advantage that MDADM has on adding drives to an array.
Edited after 1fallens post below:
I am fast coming to the conclusion that Ubuntu Desktop ( processor / ram / with the use of a GPU in the bus) maybe not a good choice for this task with enterprise hardware.
hmmm as I write this a plan is forming … which will affect the software
----added 28 jan 2025 CST–
The Ubuntu Desktop (i7-4790K w/ 32GB Ram) has not proven to be reliable in a back up role. I’ve come to the conclusion that it’s not the Software, rather the hardware .
Specifically the use of a GPU with SAS controllers, that another Mike warned me about when building the NFS Server.
2025-01-30T06:00:00Z
Hardware update has been implemented
SEE HERE FOR THE FINAL CHANGE