My original pool (Pool1, two striped six-disk RAIDZ2 vdevs) suffered a major meltdown (three disk faults in one of the vdevs) when I fired the system up again after a six-week vacation, and many files obviously did go missing in action: they still appeared in the directory, but any attempt to copy them to another drive failed. But I have copied to external drives what I can copy and the GUI shows Pool1 with 9.7TiB used. I don't recall what the "used" report was before the meltdown.
I have created another pool (Pool2, five-disk RAIDZ2), and set up a replication task to Pool2/Replicas with the intention of destroying Pool1, recreating it as an 11-disk RAIDZ3 vdev, and restoring everything from Pool2, BUT Pool2 shows only 2.7TiB used. So should I assume that the indicated 9.7TiB for the space used on Pool1 is bogus and that there is really only 2.7TiB of files there?
I have created another pool (Pool2, five-disk RAIDZ2), and set up a replication task to Pool2/Replicas with the intention of destroying Pool1, recreating it as an 11-disk RAIDZ3 vdev, and restoring everything from Pool2, BUT Pool2 shows only 2.7TiB used. So should I assume that the indicated 9.7TiB for the space used on Pool1 is bogus and that there is really only 2.7TiB of files there?
Last edited: