[zones-discuss] ZFS moving from one zone to another

2006-11-14 Thread Marlanne DeLaSource
This question is both for the ZFS forum and the Zones forum.

I have a global zone with a pool (mapool). 
I have 2 zones, z1 and z2,.
I want to pass a dataset (mapool/fs1) from z1 to z2.

Solution 1 : 
mapool/fs1 is mounted under /thing on the global zone (legacy) and I configure 
a lofs on z1 and z2.
add zonecfg:z1> add fs
zonecfg:z1:fs> set dir=/thing
zonecfg:z1:fs> set special=/fs1
zonecfg:z1:fs> set type=lofs
zonecfg:z1:fs> end
- Advantage : the fs is "seen" on both zones.
- Disadvantage : both zones can use it and I only want the "visibility" of the 
fs on one zone at a time.

Solution 2 :
zonecfg:z1> add dataset
zonecfg:z1:dataset> set name=mapool/fs2
zonecfg:z2:dataset> end
zonecfg:z2> commit
zonecfg:phil> exit
Disadvantage : I can't get rid of it when z1 is booted.

Is there a smarter solution ?

Thanks
 
 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Restart: PSARC/2006/598 Swap resource control; locked memory RM improvements

2006-11-14 Thread Steve Lawrence
> >  proposes extensions to [2], which will make swap reservation and
> >  locked memory resource controls easy to configure on a zone via
> >  zonecfg(1m).
> 
> I'm not sure if this is exactly the right place to bring this up, 
> but
> there needs to be some clarity to the user community about the
> definition of swap.  Due to the fact that it is not essential to the
> discussion of the particular ARC case, PSARC-EXT has not been Cc'd.
> 
> The key places that the term "swap" is exposed to users currently is
> vmstat(1M) and swap(1M).  A search through the relevant sysadmin
> guides and grepping through /usr/share/man turns up this somewhat
> unapproachable definition in "System Aministration Guide: Devices 
> and
> File Systems":
> 
>The Solaris OS uses the concept of virtual swap space, a
>layer between anonymous memory pages and the physical
>storage (or disk-backed swap space) that actually back these
>pages.  A system's virtual swap space is equal to the sum of
>all its physical (disk-backed) swap space plus a portion of
>the currently available physical memory.
> 
> The man pages for vmstat and swap are not especially clear as to
> whether they are talking about swap space (blocks in a swap device) 
> or
> "virtual swap space", a term that I have only seen in the Devices 
> and
> File Systems book.  That, combined with the fact that "devices and
> file systems" is not the first place a person would expect to find
> this information, frequently leads to a misunderstanding of what the
> definition of "swap" is.
> 
> As prstat is changed and resource controls are added to limit swap
> reservations, it would be extremely helpful to ensure that swap is
> clearly defined.  This likely includes a definition in a man page
> (time for swapfs(7s)?) and references to that definition in relevant
> man pages.

I agree that "swap" is generally poorly defined and misunderstood.
Hopefully, a future "memory sets + swap sets" feature make the
components of swap easier to understand and manage.

It seems reasonable to file bugs to get the appropriate manpages
updated with better definitions:

vmstat(1m)
swap(1m)
prstat(1)

swap(1m) sort of defines this in the "-s" case, but it could be better.
vmstat(1m) is lacking, and of course prstat(1) will need to be updated
anyhow for this change.

We will also update the zones/rm/container admin guide with a swap
overview when we document zone.max-swap.

-Steve

> 
> Mike
> 
> -- 
> Mike Gerdts
> http://mgerdts.blogspot.com/
___
zones-discuss mailing list
zones-discuss@opensolaris.org


[zones-discuss] Re: Restart: PSARC/2006/598 Swap resource control; locked memory RM improvements

2006-11-14 Thread Steve Lawrence
> >Good question.  These are essentially "virtual system 
> >requirements".
> > 
> >
> 
> What is the behaviour of Solaris intended to be when someone
> makes these changes (or attempts to make them) on a system
> that has no swap space?

All systems have reservable swap space.  Systems with no swap
devices use physical memory to back swap reservations.

> 
> Furthermore, why shouldn't I be able to say a zone has no swap
> space available to it - i.e. to force it to all run from RAM?

Solaris's vm system has no such concept.  All anonymous allocations
reserve swap.  I think you suggesting a zone "switch" so that an admin
can choose from one of:

A. reserve swap from disk only
B. reserve swap from memory only
C. reserve swap from disk, then memory
D. reserve swap from memory, then disk.

Currently, system behavior is C for everyone.  zone.max-swap simply
limits swap reservation.  It does not provide an interface for choosing
a swap allocation policy.  These concepts are orthogonal.  I can see
a "swap sets" feature addressing allocation policy, since "swap sets"
could be used to associate a given zone with a particular set of swap
devices.

-Steve

> 
> Darren
> 
___
zones-discuss mailing list
zones-discuss@opensolaris.org