> As one of the people who suggested that I'd > personally keep my root pool > and data pool separate... here's my take:
And this is where you got me. When you wrote "pool", I understood ZFS pool, not a dataset. A ZFS pool, at least to me, means the underlying physical storage is arranged: mirror, RAIDZ, RAIDZ2, stripe, and on physical devices. Multiple pools, again at least to me, imply multiple and separate physical devices pooled together in one of the aforementioned RAID schemes. It would appear that when you write about "root and dataset pools", you are referring to ZFS filesystems, or "datasets". Certainly nothing wrong with that at all, and *if* that's the case, we are in agreement. > The implementation of ZFS boot requires the provision > of a root pool, > which has a couple of limitations: the primary one > being that we only > support mirrored underlying devices within that pool. > See: > ttp://www.opensolaris.org/os/community/arc/caselog/200 > 6/370/onepager > (4.1.2.1). This means that the root pool may not > necessarily give me the > storage characteristics I require for my data. This is true, and from that perspective, your point of view has merit. In other words, you convinced me (:-) Now the next question: I haven't looked at the ZFS code in depth, but is it theoretically possible to modify the code so that the Solaris kernel can boot from a RAIDZ, RAIDZ2 or a striped pool? This message posted from opensolaris.org
