Date: Fri, 02 Mar 2012 10:25:09 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: freebsd-fs@freebsd.org, team@hybrid-logic.co.uk, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Another ZFS ARC memory question Message-ID: <20120302102509.Horde.6uPSdpjmRSRPUJH1lHEHc3A@webmail.leidinger.net> In-Reply-To: <20120301142826.GG97848@zxy.spb.ru> References: <1330081612.13430.39.camel@pow> <20120227181436.GA49667@server.vk2pj.dyndns.org> <20120301142826.GG97848@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Slawa Olhovchenkov <slw@zxy.spb.ru> (from Thu, 1 Mar 2012 18:28:26 +0400): > On Tue, Feb 28, 2012 at 05:14:37AM +1100, Peter Jeremy wrote: > >> > * what is the community's advice for production machines running >> > ZFS on FreeBSD, is manually limiting the ARC cache (to ensure >> > that there's enough actually free memory to handle a spike in >> > application memory usage) the best solution to this >> > spike-in-memory-means-crash problem? >> >> Are you swapping onto a ZFS vdev? If so, change back to a raw (or >> geom) device - swapping to ZFS is known to be problematic. If you > > I see kernel stuck when swapping to ZFS. This is only known problem? This is a known problem. Don't use swap on a zpool. If you want fault tollerance use gmirror for the swap paritions instead (make sure the swap partition does end _before_ the last sector of the disk in this case). Bye, Alexander. -- As of next Thursday, UNIX will be flushed in favor of TOPS-10. Please update your programs. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120302102509.Horde.6uPSdpjmRSRPUJH1lHEHc3A>