Date: Thu, 28 Jul 2005 13:24:01 -0700 From: Julian Elischer <julian@elischer.org> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@FreeBSD.org>, re@freebsd.org, Giorgos Keramidas <keramida@FreeBSD.org> Subject: Re: 6.0 VFS/VM over-runs. Was: Apparent strange disk behaviour in 6.0 Message-ID: <42E93EE1.2090009@elischer.org> In-Reply-To: <20050728135613.GD46538@darkness.comp.waw.pl> References: <42E88135.30603@elischer.org> <42E88F2B.5000108@elischer.org> <20050728082844.GW46538@darkness.comp.waw.pl> <42E898A6.6010803@elischer.org> <20050728115251.GA20091@beatrix.daedalusnetworks.priv> <20050728135613.GD46538@darkness.comp.waw.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an absolute show stopper for 6.0 Pawel Jakub Dawidek wrote: >On Thu, Jul 28, 2005 at 02:52:51PM +0300, Giorgos Keramidas wrote: >+> On 2005-07-28 01:34, Julian Elischer <julian@elischer.org> wrote: >+> > I wonder if there is some tunable that can be changed? or whether it's >+> > just a bug.. >+> > >+> > I think that a write that finds no buffer space should first free old >+> > unused buffers, and if there aren't any it should just wait. Where's >+> > alan when you need him :-) >+> >+> Setting vm.swap_idle_enabled to 0 seemed to help when I observed similar >+> problems in the past. I thought this was fixed months ago though. It >+> may be a false impression I got by forgetting to re-enable it and check >+> that this was indeed fixed. > >Setting vm.swap_idle_enabled to 0 doesn't work for me. > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42E93EE1.2090009>