Why does zfs define raidz/raidz2/mirror/stripe at the pool level instead of the
filesystem/volume level?
A sample use case: two filesystems in a eight disk pool. The first filesystems
is a stripe across four mirrors. The second filesystems is a raidz2. Both
utilizing the free space in the 8
Vizzini Sampere wrote:
Why does zfs define raidz/raidz2/mirror/stripe at the pool level instead of
the filesystem/volume level?
To take the burden away from the system admin.
Turnaround question - why *should* ZFS define an underlying
storage arrangement at the filesystem level?
A sample
On Wed, 2007-01-17 at 20:34 +1100, James C. McPherson wrote:
Vizzini Sampere wrote:
Why does zfs define raidz/raidz2/mirror/stripe at the pool level instead of
the filesystem/volume level?
To take the burden away from the system admin.
Turnaround question - why *should* ZFS define an
