Jesus Cea wrote:
Read performance [when using zfs set copies=2 vs a mirror] would double,
and this is very nice
I don't see how that could be the case. Either way, the reads should be able
to fan out over the two disks.
--matt
___
zfs-discuss
Jesus Cea wrote:
Would ZFS boot be able to boot from a copies boot dataset, when one of
the disks are failing?. Counting that ditto blocks are spread between
both disks, of course.
You can not boot from a pool with multiple top-level vdevs (eg, the copies
pool you describe). We hope to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know that first release of ZFS boot will be support single disk and
mirroring configurations. With ZFS copies support in Solaris 10 U5 (I
hope), I was wondering about breaking my current mirror and using both
disks in stripe mode, protecting the
Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know that first release of ZFS boot will be support single disk and
mirroring configurations. With ZFS copies support in Solaris 10 U5 (I
hope), I was wondering about breaking my current mirror and using both
disks in stripe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Darren J Moffat wrote:
Why would you do that when it would reduce your protection and ZFS boot
can boot from a mirror anyway.
I guess ditto blocks would be protection enough, since the data would be
duplicated between both disks. Of course,
Jesus Cea wrote:
Darren J Moffat wrote:
Why would you do that when it would reduce your protection
and ZFS boot
can boot from a mirror anyway.
I guess ditto blocks would be protection enough, since the
data would be
duplicated between both disks. Of course, backups are your friend.
Moore, Joe wrote:
It would be really nice if there was some sort of
enforced-ditto-separation (fail w/ device full if unable to satisfy) but
that doesn't exist currently.
How would that be different to a mirror ?
I guess it is different to a mirror because only some datasets in the
pool
