7 ms·
If you can have downtime: you could create a new pool, turn off writes to the old pool, snapshot the entire pool into the new pool using the built in snapshot &
by gravypod 7y ago
If you can have downtime: you could create a new pool, turn off writes to the old pool, snapshot the entire pool into the new pool using the built in snapshot & transfer mechanics, and then kill the old pool.
If you're ok with write performance degradation & doing multiple resilvers than what the op did is fine too.
- tracker1 7y agoThat assumes you have enough extra spaces to do it and you didn't start full. Ex: just bought a used Dell R710 with 6 bays, it came with 2TB drives... plan is to play around a bit with those... but I don't have an extra, supported controller with enough slots (even if the cover is off) to populate it while I would migrate. In the end, it'll be full of shucked 8tb drives, but pretty sure I'll just start over at that point. My old nas' drives are 6yo in a decade old synology box, and my trust level is failing before any drives do.
- gravypod 7y agoSomething that's important to consider is if your drives can handle a resilver. Each resilver is essentially reading the entire disk (with lots of asterisks) while setting up a parallel zfs system to provision your disks and using the transfer I described will only read your systems fs once. You don't even need to use the same system. You can setups a different system, run the transfer, turn off the main system, swap the disks. It's a hastle but it's an option at your disposal.
- tracker1 7y agoIf I'm using Raid-Z2, isn't there a way to drop the old drive and add a new drive to take its' place?