No subject

Unknown Unknown
Mon Mar 22 01:40:37 PDT 2010

16061 at>
From: Francois Tigeot <ftigeot at>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Mon, 22 Mar 2010 09:39:07 +0100
List-Post: <mailto:bugs at>
List-Subscribe: <mailto:bugs-request at>
List-Unsubscribe: <mailto:bugs-request at>
List-Help: <mailto:bugs-request at>
List-Owner: <mailto:owner-bugs at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201003211914.o2LJEBNo016061 at>
Sender: bugs-errors at
Errors-To: bugs-errors at
Lines: 19
X-Trace: 1269247340 55375
Xref: dragonfly.bugs:11558

On Sun, Mar 21, 2010 at 12:14:11PM -0700, Matthew Dillon wrote:
> :>     Try setting it to 40 (it defaults to 23).  The max value is 64
> :>     which will effectively put all non-memory-mapped file data on the
> :>     inactive queue, including any data which is repeatedly accessed.
>     I'd like to know if this solves your particular problem (the paging
>     issue, not the crashing issue), and if so I will change the default
>     cycle point for the release.  So play with it.

With vfs.vm_cycle_point = 40 my server was much more responsive this morning.
Almost no programs had to be paged in when first accessed.

So far, so good.

I have now decreased vm_cycle_point to 32.

Francois Tigeot

More information about the Bugs mailing list