Re: [zones-discuss] Zones on NFS

2007-04-17 Thread Jason King
On 4/17/07, Mike Gerdts [EMAIL PROTECTED] wrote: On 4/17/07, Matty [EMAIL PROTECTED] wrote: Howdy, Ben brought up the idea of running zones on NFS file systems a few months back: http://www.opensolaris.org/jive/thread.jspa?messageID=81240#81240 Have the zones team given any consideration

Re: [zones-discuss] Will Zones Memory Caps let you specify more than physically installed system memory?

2008-06-17 Thread Jason King
On Tue, Jun 17, 2008 at 8:07 PM, Jim Nissen [EMAIL PROTECTED] wrote: Hi all, Got a question from a customer, and can't seem to find an answer. Let's say they have multiple zones, and are specifying physical memory caps on all of them. If they have, say, 16GB of memory, is there anything that

[zones-discuss] cmn_err / zcmn_err

2008-08-11 Thread Jason King
I'm working on rfe 6613349 suid not allowed message could be better, and one issue is that the current error message uses cmn_err() (usr/src/uts/common/os/exec.c:613). I'm pretty sure this should use zcmn_err(), since (to me at least) I would think the message should (at least) go to the zone

[zones-discuss] zoneroot on nfs?

2008-10-21 Thread Jason King
I haven't found any documentation (yet, still looking), that says anything either way, but I'm wondering to facilitate zone migration if you can place a zone root on an NFS filesystem? Obviously would only be mounted on 1 server at any given time, but outside of that, just wondering if it should

[zones-discuss] Code Review for 6613349 setuid not allowed message could be more useful

2008-11-12 Thread Jason King
I'm looking for reviewers for '6613349 setuid not allowed message could be more useful'. I've tested it on a b101 system without any issues. It's pretty straightforward (and small) -- just modifying the message to display the filesystem path (instead of the device number) and making it zone

Re: [zones-discuss] Code Review for 6613349 setuid not allowed message could be more useful

2008-11-12 Thread Jason King
On Wed, Nov 12, 2008 at 12:46 PM, [EMAIL PROTECTED] wrote: I'm looking for reviewers for '6613349 setuid not allowed message could be more useful'. I've tested it on a b101 system without any issues. It's pretty straightforward (and small) -- just modifying the message to display the

[zones-discuss] Creating ZFS filesystems prior to zoneadm install

2009-01-22 Thread Jason King
Is there any way to create non-legacy, canmount=yes filesystems with set mountpoints for a zone prior to zoneadm install? I'm trying to do some zone creation automation, and one of the things is a per-zone, writable /usr/local (yes it's not 'standard' but then I can count on one hand the number

Re: [zones-discuss] Creating ZFS filesystems prior to zoneadm install

2009-01-25 Thread Jason King
On Sun, Jan 25, 2009 at 9:59 AM, Jeff Victor jeff.j.vic...@gmail.com wrote: Hi Jason, I frequently recommend creating a writable /usr/local under the read-only /usr to solve this problem. One simple method to do this is: zonecfg -z myzone add fs set special=/mypool/zones/usr-local set

Re: [zones-discuss] Creating ZFS filesystems prior to zoneadm install

2009-01-26 Thread Jason King
method to do this is: zonecfg -z myzone add fs set special=/mypool/zones/usr-local set dir=/usr/local set type=lofs end exit Will that work for you? --JeffV On Thu, Jan 22, 2009 at 1:17 PM, Jason King ja...@ansipunx.net wrote: Is there any way to create non-legacy, canmount=yes

Re: [zones-discuss] Code Review for 6613349 setuid not allowed message could be more useful

2009-02-01 Thread Jason King
On Fri, Nov 14, 2008 at 11:21 AM, casper@sun.com wrote: On Thu, Nov 13, 2008 at 3:05 AM, casper@sun.com wrote: Originally I did that, but there was concern v_path might not always be correct (or available) (such as renames or with hard links IIRC), and so might generate a confusing

Re: [zones-discuss] ZFS ARC cache issue

2010-06-04 Thread Jason King
Are you sure fusion isn't checking the amount of available memory itself and just deciding to abort? It wouldn't be unprecendeted -- if you run Oracle RDBMS on NFS mounts, it refuses to start unless it sees explicit mount options provided for the database filesystems (even when they are merely