> Actually, you do want /usr and much of /var on the root pool, they > are integral parts of the "svc:/filesystem/local" needed to bring up > your system to a useable state (regardless of whether the other > pools are working or not).
Ok. I have my feelings on that topic but they may not be as relevant for ZFS. It may be because I tried to avoid single points of failure on other systems with techniques that don't map to ZFS or Solaris. I believe I can bring up several OS without /usr or /var although they complain they will work. But I'll take your point here. > Depending on the OS versions, you can do manual data migrations > to separate datasets of the root pool, in order to keep some data > common between OE's or to enforce different quotas or compression > rules. For example, on SXCE and Solaris 10 (but not on oi_148a) > we successfully splice out many filesystems in such a layout > (the example below also illustrates multiple OEs): Thanks, I have done similar things but I didn't know if they were "approved". > And you can not boot from any pool other than a mirror or a > single drive. Rationale: a single BIOS device must be sufficient > to boot the system and contain all the data needed to boot. Definitely important fact here. Thanks for all the info! _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
