From owner-freebsd-current Tue Jun 18 20:58:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03102 for current-outgoing; Tue, 18 Jun 1996 20:58:47 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA03083 for ; Tue, 18 Jun 1996 20:58:40 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id XAA18921; Tue, 18 Jun 1996 23:56:08 -0400 (EDT) Date: Tue, 18 Jun 1996 23:57:12 -0400 (EDT) From: Brian Tao To: David Greenman cc: Matt Day , freebsd-current@FreeBSD.org Subject: Re: Kernel panic in fsync, 2.2-960501-SNAP In-Reply-To: <199606121213.FAA00941@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Jun 1996, David Greenman wrote: > > Since this is -current, I would strongly suggest SUPing the latest > stuff. There were a great deal of serious VM system bugs in the 0501 > snapshot that have just recently been worked out. I guess that would be my next step then. The patch Matt provided was able to get through 6 days of uptime on each of the two shell servers here, but one of them crashed in fsync() today, again caused by an emacs process. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"