From owner-freebsd-hackers Thu Oct 29 21:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29961 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 21:22:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29953 for ; Thu, 29 Oct 1998 21:22:05 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40365>; Fri, 30 Oct 1998 16:21:23 +1100 Date: Fri, 30 Oct 1998 16:21:51 +1100 From: Peter Jeremy Subject: sync writes with softupdates enabled To: hackers@FreeBSD.ORG Message-Id: <98Oct30.162123est.40365@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just installed 3.0-RELEASE on the machine destined to be our new news server. Whilst testing it with soft updates enabled, I'm seeing a lot of sync writes onto /usr: /dev/wd0s1f on /usr (local, soft-updates, writes: sync 32910 async 4955) With /usr mounted asynchronously rather than soft updates enabled, I also saw lots of synchronous writes. The writes are definitely a result of innd - nothing else much is running and pausing innd makes the I/O stop. I've looked at a ktrace of innd and can't see anything that would obviously cause it to do sync writes (no fsync() or open(O_SYNC) calls). It's inn-1.7.2 as per the ports with the exception that MMAP is enabled for dbz. All I can think of is that the MMAP'd history file is causing the kernel to unnecessarily perform sync writes to try and keep the MMAP and VFS images in sync. Any ideas? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message