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 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 disk pool as needed.
No, that's not how it works.
You create the zpool. At creation time you specify whether it will
be a stripe or raidz or raidz2 or whatever.
From that pool you create as many filesystems as you need.
If from those 8 disks you want two different underlying types
of storage layout, you would create two pools.
James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
http://www.jmcp.homeunix.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
