3 ms·

Would it not have been easier to just mount the destroyed old pool or recovering the dataset from the history ring buffer? zpool import -D https://openzfs.git

Would it not have been easier to just mount the destroyed old pool or recovering the dataset from the history ring buffer? zpool import -D https://openzfs.github.io/openzfs-docs/man/master/8/zpool-import.8.html https://openzfs.github.io/openzfs-docs/man/master/8/zpool-im... I haven't tried this, but I gather from the blog post that it would have been much simpler as it didn't require any of the encryption stuff.

Dylan16807 1y ago
There wasn't a destroyed pool, it's the harder version of trying to rewind time on the filesystem. It's worth trying once the disks are fully backed up, but it's fussy enough that I can understand why they made it plan B.
- mentalpagefault 1y ago
  It didn't make the cut for the article, but I do recall trying to import older uberblocks still in the label ring buffer with zpool import -T at some point, but none were before the zfs destroy. I assume that was because TrueNAS logs to the .system dataset and presumably wrote through the entire ring buffer before I got to it.