From owner-freebsd-current Sun Dec 19 11:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F0516151FB for ; Sun, 19 Dec 1999 11:32:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA06700; Sun, 19 Dec 1999 11:32:38 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 11:32:38 -0800 (PST) From: Matthew Dillon Message-Id: <199912191932.LAA06700@apollo.backplane.com> To: Vallo Kallaste Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird story with dump | restore References: <199912171648.IAA29595@gndrsh.dnsmgr.net> <199912171732.JAA63489@apollo.backplane.com> <19991219111237.A37996@myhakas.matti.ee> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Fri, Dec 17, 1999 at 09:32:04AM -0800, Matthew Dillon wrote: : :> sysctl -a | fgrep dirty :> sysctl -w vfs.lodirtybuffers=X :> sysctl -w vfs.hidirtybuffers=Y : :Matt, I've tried your patch to sys/kern/vfs_bio.c, made no difference. :Lowering the vfs.hidirtybuffers from 221 to 110 helps as before. The :vfs.lodirtybuffers sysctl is gone for some reason. Oh my. Maybe we have two problems here. Alfred had similar problems and the patch fixed it right up. Try running a 'top -S -s1' while you are running your test, with my patch but without doing the sysctl's, and tell me what the various programs block on when the problem occurs (buf_daemon and whatever program is causing the hicup). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message