summaryrefslogtreecommitdiffstats
path: root/sys/nfsclient
diff options
context:
space:
mode:
authordg <dg@FreeBSD.org>1995-03-23 09:43:40 +0000
committerdg <dg@FreeBSD.org>1995-03-23 09:43:40 +0000
commit1488c6e0c62a155071e81c4a270401ef6fb9b704 (patch)
tree58521f0be14a492f8fdec6bab047ebe18316b7a0 /sys/nfsclient
parent76cc5d1e93a036428c82f154c92018a37d676d97 (diff)
downloadFreeBSD-src-1488c6e0c62a155071e81c4a270401ef6fb9b704.zip
FreeBSD-src-1488c6e0c62a155071e81c4a270401ef6fb9b704.tar.gz
Deleted bogus DIAGNOSTIC "nfs_fsync: dirty" message. This can and does
happen normally when there is heavy write activity to a file since the vnode isn't locked (NFS plays fast and loose with vnode locks). This change "fixes" PR#267.
Diffstat (limited to 'sys/nfsclient')
-rw-r--r--sys/nfsclient/nfs_vnops.c5
1 files changed, 1 insertions, 4 deletions
diff --git a/sys/nfsclient/nfs_vnops.c b/sys/nfsclient/nfs_vnops.c
index b4a9baf..1cfe1a0 100644
--- a/sys/nfsclient/nfs_vnops.c
+++ b/sys/nfsclient/nfs_vnops.c
@@ -34,7 +34,7 @@
* SUCH DAMAGE.
*
* @(#)nfs_vnops.c 8.5 (Berkeley) 2/13/94
- * $Id: nfs_vnops.c,v 1.12 1995/02/03 06:46:24 davidg Exp $
+ * $Id: nfs_vnops.c,v 1.13 1995/03/16 18:15:41 bde Exp $
*/
/*
@@ -2200,9 +2200,6 @@ loop:
}
}
if (vp->v_dirtyblkhd.lh_first) {
-#ifdef DIAGNOSTIC
- vprint("nfs_fsync: dirty", vp);
-#endif
goto loop;
}
}
OpenPOWER on IntegriCloud