>>>>> "tr" == Timothy Renner <timothy.ren...@gmail.com> writes:
tr> zfs set copies=2 zfspool/test2
'copies=2' says things will be written twice, but regardless of
discussion about where the two copies are written, copies=2 says
nothing at all about being able to *read back* your data if one of the
copies disappears. It only promises that the two copies will be
written. This does you no good at all if you can't import the pool,
which is probably what will happen to anyone who has relied on
copies=2 for redundancy.
The discussion about *where* the copies tend to be written is really
impractical and distracting, IMO.
The chance that the copies won't be written to separate vdev's is not
where the problem comes from. You can't import a pool unless it has
enough redundancy at vdev-level to get all your data, so copies=2
doesn't add much. The best copies=2 will do is give you a slightly
better shot at evacuating the data from a slowly-failing drive. If
anyone at all should be using it, certainly I don't think someone with
more than one drive should be using it.
pgp2ATsq8cq9a.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
