Thanks. I've been reading through the zfs man page (converted to PDF to make it more convenient) and I'm starting to get it, lol
There appear to be quite a few options that I'll need to read more into and hopefully understand. Much learning to do.
I recall seeing this in the zpool man page:
ZFS supports a rich set of mechanisms for handling device failure and data corruption. All metadata and data is checksummed, and ZFS automatically repairs bad data from a good copy when corruption is detected.
In order to take advantage of these features, a pool must make use of some form of redundancy, using either mirrored or raidz groups. While ZFS supports running in a non-redundant configuration, where each root vdev is simply a disk, this is strongly discouraged. A single case of bit corruption can render some or all of your data unavailable.
So I assume with a pool of a single disk, if a file became corrupted, it would know it was corrupted, but wouldn't be able to revert to the uncorrupted version, but would alert you in some fashion?
I have a few disks that I was planning on not using in my 10 disk RAID10 set and I'm wondering now what would be the best way to utilize them.
One 2TB Western Digital Black
One 3TB Hitachi Deskstar
Hmmm, now that I think about it, I have another Hitachi 2TB Deskstar in an external single disk enclosure that I could swap with the 3TB and then would be able to mirror the two 2TB drives.
I obviously have more planning to do!