On 01/19/11 11:54 AM, Darren Kenny wrote:
On 18/01/2011 21:21, Dave Miner wrote:
On 01/18/11 11:22 AM, Drew Fisher wrote:
Dermot,
On 1/18/11 7:53 AM, Dermot McCluskey wrote:
,,,
- Q: where do<swap> and<dump> go? under<target> or<logical>?
Honestly, I don't know yet. For Zvol based swap/dump, perhaps that
could be an attribute to a<zvol> object which is a child under a
<zpool> object? is_swap (true|false) "false" or something like that?
For UFS based ... I have no idea. Are we even supporting UFS swap/dump?
There are some corner-case advantages to swap and dump slices (don't say
UFS, because it doesn't involve UFS :-) over zvol's at present that
might appeal to specific situations. If we can easily support them in
the syntax, that would be good, even if we don't implement support in
the code immediately (or ever).
I believe the last time we met (Friday) to talk about targets, we talked about
adding a 'swap=(true|false}' attribute to the<slice> tag, defaulting to 'false'
- and I still feel this is the best approach to allow creation of a swap slice.
This would handle the swap on a slice or not.
How would one enforce swap/dump to not be created ?
Currently if swap/dump is not specified it will be created by default
(if there is enough space).
In pre-cud schema, setting size to "0" would result in swap not being
created.
In current cud target.dtd there is a no_swap and no_swap attribute which
defaults to False, however if set to true indicates to not create
swap/dump, something like this needs to be maintained here.
cheers
Matt
Thanks,
Darren.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
