From owner-freebsd-hackers Tue Aug 8 13:25:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 6F02237B735 for ; Tue, 8 Aug 2000 13:25:40 -0700 (PDT) (envelope-from float@firedrake.org) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13MFuq-0007Jp-00; Tue, 08 Aug 2000 21:24:00 +0100 Date: Tue, 8 Aug 2000 21:24:00 +0100 From: void To: Mitja Horvat Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1-RELEASE problem writing to async mounted filesystem Message-ID: <20000808212400.B26432@firedrake.org> References: <200008081606.SAA11004@akira.hermes.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <200008081606.SAA11004@akira.hermes.si>; from mitja.horvat@hermes.si on Tue, Aug 08, 2000 at 06:03:08PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 06:03:08PM +0200, Mitja Horvat wrote: > > Hi, > > I recently upgraded to FreeBSD 4.1-RELEASE(CD image). I noticed that while > writing > to an asynchronously mounted filesystem(mount -o async / ...) all other IO > operations to the FS are almost blocked. I have only one asynchronously > mounted > partition(/) and the following shell script makes the machine unresponsive > so I cannot > even telnet to it: > > while true; do rm -f foo; dd if=/dev/zero of=foo bs=1024k count=256; done > > 4.0-RELEASE does a much better job at handling similar situations... > > I'm using softupdates, but even without them the problem persists. There's no reason to use softupdates and async together. SU gets you the same benefits, but much more safely. > This does not happen if the fs is mounted synchronously, but I also get > MUCH slower IO > throughput(800kb/s compared to 12MB/s with async). Mounted sync or noasync? They're not the same thing. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message