Lori Alt wrote: >> Since it seems that we won't be swapping on ZVOLS I need to find out >> more how we will be providing swap and dump space in a root pool. >> > The current plan is to provide what we're calling (for lack of a > better term. I'm open to suggestions.) a "pseudo-zvol". It's > preallocated space within the pool, logically concatenated by > a driver to appear like a disk or a slice. It's meant to be a low > overhead way to emulate a slice within a pool. So no COW or > related zfs features are provided, except for the ability to change > its size without having to re-partition a disk. A pseudo-zvol > will support both swap and dump.
Just so it is clear, what are the full list of "related features" that won't be supported with these non COW volumes ? For swap (but less so for dump) we MUST be able to keep raid and the probably means checksuming as well (otherwise we can bring down the system as a result of a disk failure when paging in or out). I think for encrypted swap it is probably best we do that inside the VM system as a separate project rather than as part of ZFS. -- Darren J Moffat _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
