Zones do not have default memory limits. A zone's processes are allowed to use as much RAM and swap as they want. If you want to limit there usage, resource controls exist to do that.
Fork calls fail when there isn't enough swap space. It returns with error ENOMEM, which is 12. The second failure in your log below returned a status of 12. Is the system low on free swap space when this problem occurs? Jim Caron - ITCTO wrote: > Folks, > > I have an issue where a zone seems to be rnning out of memory. is there > a limit to how much memory a zone can use? If so, how do you overcome > this limit? we are getting the following errors: > > *** SERVICE NAME:(SYS$BACKGROUND) 2007-07-25 07:49:55.187 > *** SESSION ID:(444.1) 2007-07-25 07:49:55.187 > *** 2007-07-25 07:49:55.187 > Process startup failed, error stack: > ORA-27300: OS system dependent operation:fork failed with status: 2 > ORA-27301: OS failure message: No such file or directory > ORA-27302: failure occurred at: skgpspawn5 > *** 2007-07-25 07:49:57.204 > Process startup failed, error stack: > ORA-27300: OS system dependent operation:fork failed with status: 12 > ORA-27301: OS failure message: Not enough space > ORA-27302: failure occurred at: skgpspawn3 > > error 4030 detected in background process > ORA-04030: out of process memory when trying to allocate bytes (,) > > > Does anyone have some insight on this? > > thanks > -- -------------------------------------------------------------------------- Jeff VICTOR Sun Microsystems jeff.victor @ sun.com OS Ambassador Sr. Technical Specialist Solaris 10 Zones FAQ: http://www.opensolaris.org/os/community/zones/faq -------------------------------------------------------------------------- _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
