From owner-freebsd-smp  Fri Sep  8 13:19: 4 2000
Delivered-To: freebsd-smp@freebsd.org
Received: from magnesium.net (toxic.magnesium.net [207.154.84.15])
	by hub.freebsd.org (Postfix) with SMTP id 5C43B37B505
	for <freebsd-smp@FreeBSD.org>; Fri,  8 Sep 2000 13:19:01 -0700 (PDT)
Received: (qmail 44052 invoked by uid 1142); 8 Sep 2000 20:19:00 -0000
Date: 8 Sep 2000 13:19:00 -0700
Date: Fri, 8 Sep 2000 13:18:52 -0700
From: Jason Evans <jasone@canonware.com>
To: Robert Watson <rwatson@FreeBSD.org>
Cc: freebsd-smp@FreeBSD.org
Subject: Re: SMPng: ``Giving up on 1 buffer''
Message-ID: <20000908131852.B19447@blitz.canonware.com>
References: <Pine.NEB.3.96L.1000908132333.49300B-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.NEB.3.96L.1000908132333.49300B-100000@fledge.watson.org>; from rwatson@FreeBSD.org on Fri, Sep 08, 2000 at 01:25:06PM -0400
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Fri, Sep 08, 2000 at 01:25:06PM -0400, Robert Watson wrote:
> I recently cvsup'd to a recent -CURRENT, past the SMPng commit.
> Everything seems hunky dory, except for the fact that during my last
> shutdown, I was surprised to see that the disk sync'ing failed, with one
> buffer not committed.  On bootup, the file system was not clean, requiring
> a fsck which showed no problems.  I assume that this is related somehow.

Jake Burkholder also experiences this behavior, but it has never happened
to me.  So, it seems to be a hit and miss thing.  You get hit.

Jason


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