From owner-freebsd-current  Sun Sep 27 02:06:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA05023
          for freebsd-current-outgoing; Sun, 27 Sep 1998 02:06:12 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04972
          for <freebsd-current@FreeBSD.ORG>; Sun, 27 Sep 1998 02:05:55 -0700 (PDT)
          (envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
	by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id CAA00415;
	Sun, 27 Sep 1998 02:05:11 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id CAA11810;
	Sun, 27 Sep 1998 02:05:10 -0700 (PDT)
Received: (from gdonl@localhost)
	by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id CAA01883;
	Sun, 27 Sep 1998 02:05:09 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199809270905.CAA01883@salsa.gv.tsc.tdk.com>
Date: Sun, 27 Sep 1998 02:05:08 -0700
In-Reply-To: Peter Wemm <peter@netplex.com.au>
       "Re: Softupdates panics" (Sep 27,  2:43pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Peter Wemm <peter@netplex.com.au>,
        Ollivier Robert <roberto@keltia.freenix.fr>
Subject: Re: Softupdates panics
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sep 27,  2:43pm, Peter Wemm wrote:
} Subject: Re: Softupdates panics
} 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.

That makes more sense.  It doesn't seem to make sense to use both softupdates
and async.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message