From owner-freebsd-current Mon Aug 31 11:15:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00492 for freebsd-current-outgoing; Mon, 31 Aug 1998 11:15:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00486 for ; Mon, 31 Aug 1998 11:15:54 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA00397; Mon, 31 Aug 1998 19:14:00 +0100 (BST) Date: Mon, 31 Aug 1998 19:14:00 +0100 (BST) From: Doug Rabson To: John Polstra cc: current@FreeBSD.ORG Subject: Re: softupdates panic In-Reply-To: <199808302016.NAA09085@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Aug 1998, John Polstra wrote: > This is from a soft-updates -current kernel from August 26. All > filesystems were mounted with soft updates. The system that crashed > was doing NFS server activity at the time. A remote machine was > building a port in a directory mounted (nfsv2) from the server that > crashed. I have the -g kernel and core dump in case anybody is > interested. > > Also, we still seem to have the bug in which fsck turns off the > soft-updates bit when it recovers the FS (root in this case). I just got this one too. The machine was doing NFS server work only with a remote machine building a port in an nfsv3 mounted directory. Unfortunately I don't have the core dump but I can repeat the crash extremely easily. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message