From owner-freebsd-current  Mon Nov 23 14:12:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA24413
          for freebsd-current-outgoing; Mon, 23 Nov 1998 14:12:02 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spook.navinet.net (spook.navinet.net [206.25.93.69])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24351
          for <current@FreeBSD.ORG>; Mon, 23 Nov 1998 14:11:55 -0800 (PST)
          (envelope-from forrie@navinet.net)
Received: from forrie (black.navinet.net [206.25.93.86])
	by spook.navinet.net (8.9.1/8.9.1) with SMTP id RAA00313
	for <current@FreeBSD.ORG>; Mon, 23 Nov 1998 17:11:44 -0500 (EST)
Message-Id: <4.1.19981123164943.00a9ae60@206.25.93.69>
X-Sender: forrie@206.25.93.8
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 23 Nov 1998 16:50:39 -0500
To: current@FreeBSD.ORG
From: Forrest Aldrich <forrie@navinet.net>
Subject: Re: Random craches under heavy(?) disk activity
In-Reply-To: <3659F860.E8309B47@ein-hashofet.co.il>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I haven't had another reboot since the last time I reported it.

At the time, I recall seeing a vfs_* file updated in cvs, and I'm 
wondering if that fixed the problem.   I just did a build world,
no problems.


Forrest

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