The least bad imo is making a two drive raidz1 then expanding it.
The least bad imo is making a two drive raidz1 then expanding it.
So the broken pool is kinda stupid and you shouldn’t do it, you will be running without parity the whole time but if you want to risk it it does work.
Or… If you have the drives and space, you can combine a bunch of smaller drives with mdadm (assuming Linux but freebsd has geom I think) and then use that as your third drive, then once everything is copied do a zpool replace. That way you keep full parity the whole time.
Edit: latest version of zfs supports raidz expansion. So you could create a 2 drive raidz1 then copy everything over then expand it. You will still be running your source disk without parity but at least the destination would be safe.
I know you kid but even the 3ds fits a decent number of lines on screen.
My man, most of us aren’t connecting to our mainframes on VT20s these days. Even on my phone screen the three extra lines nano takes over vi aren’t a problem.
Also if you have the time to go through all that you have the time to learn ctrl+x.
What usually happens in Guatemala is you’ll take one ride with them through Uber and if they seem cool and are from your area you get their number and just message them in the future to ask for a ride.
Just did it to test on a couple of files, worked fine.