Hi Dave,
elided...
The scope of a swap or dump device is global and not specific to a pool.
- Should we have an "automatic" specification for swap/dump (in other
words, use the algorithm that the interactive installers use), or is
its absence expected to imply automatic behavior in AI? If that's the
case, do we need a "none" to disable their creation?
No, we don't need a none. Since this is a subelement of the target
element and not required, their absence means we default to calculating
it. If specified we use the values specified.
OK, so if I don't specify swap/dump targets at all, then I don't get
any? I wonder if we should default this differently, though, so that
a standard install might have a more terse document. It's unusual to
not want swap or dump, after all (and there are some who claim that
having no dump shouldn't even be allowed).
No, if you don't specify any swap or dump targets you get the default
swap target. I am not sure about dump, but I know we calculate and
create the default swap device.
Do you want the user to have to specify swap/dump to get these? And
default to nothing?
- The comment about swap and dump should be more specific that merely
specifying size would create them with a specific name on the (first?
per comment above) root pool.
Yes, I agree. It should be more specific. What I am saying is that if a
size is given, we will create swap in the root pool, otherwise if zvol
data is given we will use that zvol.
- I assume we can specify multiple swap devices?
No, not as I currently have it specified. I can modify this to allow for
multiple swap devices.
I think we should; it's reasonably common.
I added this.
- Doesn't seem to be any way to specify swapping on a slice. We do
this in some cases currently, though, and right now the pathological
behavior of ZFS swap when exhausted makes it even preferable.
I thought that swap had to be on a zfs zvol moving forward. I can
certainly change this spec to allow for specifying a slice as one of the
possibilities. What about using a slice for a dump device?
Nobody's done any work to remove slices as legal targets for swap or
dump, though I'm mostly concerned with swap here. For now I'd let the
model support it in both cases, I guess
Ok, I added this.
thanks,
sarah
.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
