Mario Goebbels wrote:
I just perused through the ZFS Best Practices wiki entry on solarisinternals.com and it says that for ZFS boot, the pool is restricted to one disk and mirror pools. Is this still applicable to build 62 and the mentioned "new code"?
I'm not sure what you mean by "one disk." Today, it works with mirrors and your BIOS must be able to see all of the drives in a root pool. Fortunately these requirements can be satisfied by a vast majority of the boxes out there.
The availability of the "zpool set bootfs" command suggests that you might be able to tell ZFS to give that specific filesystem in a pool a special treatment, as such not striping the data going into that filesystem. How far off am I with my guess?
Special treatment, yes. But striping is not a file system attribute, it is a pool attribute. What I envision happening is that you may have several different root file systems (all in one pool) over time -- especially if you use LiveUpgrade. You may also have a different policy for that file system. For example, in a single disk laptop, I set the policy of copies=1 for the OS because it is read-mostly and if a file rots, I can reload it from media. OTOH for my home directory's file system I set copies=2 because I like my data and want more protection for those things that are not on a DVD somewhere.
Will I be able to create a single multi disk pool and be able to boot off it?
Yes. -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
