Richard Elling wrote: > Additional use case below... > > I look at it a little differently. The copies parameter is set per > file system (or zvol,) not per storage pool. Mirroring and raidz[12] > are set per storage pool. This flexibility allows you to set different > policies on a file system than you might on a pool. For example, > my wife's home directory (which contains her pictures) has > copies=2. But the OS on the same storage pool has copies=1 > because I can always reload the OS from media, if or when ZFS > complains about corruption in the OS file system. If you have > very important data and are paranoid about losing it, then you > might configure a file system with copies=2 or 3, regardless of > the storage pool configuration. One side affect of this strategy > is that you can't really say, categorically, that copies=2 will > always use 2x the space, especially if you also enable compression... > space accounting just gets... fuzzier... a distant ship's smoke on > the horizon...
Absolutely, excellent example. benr. _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
