From owner-freebsd-current Mon Feb 1 10:31:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25135 for freebsd-current-outgoing; Mon, 1 Feb 1999 10:31:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25118; Mon, 1 Feb 1999 10:31:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id KAA07335; Mon, 1 Feb 1999 10:30:57 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Feb 1999 10:30:57 -0800 (PST) From: Matthew Dillon Message-Id: <199902011830.KAA07335@apollo.backplane.com> To: Bjoern Fischer Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: nuts'n'bolts in vfs_bio References: <19990129094616.A555@frolic.no-support.loc> <199901290923.BAA75985@apollo.backplane.com> <19990129211554.A349@broccoli.no-support.loc> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :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