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 affirming the default behavior). If you can, I'd try using truss or such -- I'd be interested to see if it's running vmstat or looking at some kstats. On Fri, Jun 4, 2010 at 11:04 AM, James Carlson <carls...@workingcode.com> wrote: > Petr Benes wrote: >>> That leaves unanswered the underlying question: why do you need to do >>> this at all? Isn't the ZFS ARC supposed to release memory when the >>> system is under pressure? Is that mechanism not working well in some >>> cases ... ? >> >> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6522017 >> >> " ... Even if the ZFS ARC subsequently frees memory, the kernel cage does >> not shrink. It cannot shrink, because pages from the ZFS ARC were >> interspersed with other kernel pages, so the free space in the >> physical address range of the cage is fragmented when the ZFS pages >> are released. The remaining kernel pages cannot be moved to compress >> the cage, as kernel memory inside the cage is not relocatable. ..." > > Sure ... but that refers specifically to DR-related issues, and that's > not what the original poster complained about. His original message > said that he was having trouble with a large application (Oracle Fusion) > running on a system using ZFS. Does Fusion really need contiguous > kernel memory (why?) or is there something else going on here? > > -- > James Carlson 42.703N 71.076W <carls...@workingcode.com> > _______________________________________________ > zones-discuss mailing list > zones-discuss@opensolaris.org > _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
