From owner-freebsd-current Sat Sep 26 23:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19021 for freebsd-current-outgoing; Sat, 26 Sep 1998 23:45:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18974 for ; Sat, 26 Sep 1998 23:45:07 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id OAA11696; Sun, 27 Sep 1998 14:43:03 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199809270643.OAA11696@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: freebsd-current@FreeBSD.ORG Subject: Re: Softupdates panics In-reply-to: Your message of "Sat, 26 Sep 1998 22:03:33 +0200." <19980926220333.A20259@keltia.freenix.fr> Date: Sun, 27 Sep 1998 14:43:02 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > According to Don Lewis: > > I hadn't heard this. I don't know why that would be true. > > I remember people getting panics when running noatime with SU. I've got a > few myself (although they were more unstable than now). I thought it was async that was causing the problems. One of the main problems was that softupdates was doing a 'write everything' FSYNC vnode op and expecting all modified data to be written out. The async mount option "broke" the semantics of fsync() so that it didn't really wait until everything was on disk, so softupdate's sanity checks caught it. I think I saw somebody (Bruce?) change the semantics of VOP_FSYNC() back again. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message