From owner-freebsd-stable Mon Feb 1 10:55:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28230 for freebsd-stable-outgoing; Mon, 1 Feb 1999 10:55:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28205; Mon, 1 Feb 1999 10:55:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id KAA13162; Mon, 1 Feb 1999 10:54:47 -0800 Date: Mon, 1 Feb 1999 10:54:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon cc: Bjoern Fischer , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: nuts'n'bolts in vfs_bio In-Reply-To: <199902011830.KAA07335@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen this for a non-NFS case. On Mon, 1 Feb 1999, Matthew Dillon wrote: > > :Hello Matthew, > : > :thank you for reviewing vfs_bio.c. Your patch seems to > :solve the problem with NFS writes remaining uncommitted. > :At the time I can't see any NFS related data corruption. > : > :But when shutting down the server it still panics complaining > :about dirty bufs. (happens in 9 out of 10 times). > : > : Bjoern > > I haven't been able to reproduce this one yet. I can see how there > might be dirty buffers on the client, but there shouldn't be dirty buffers > on the server. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message