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.
This commit is contained in:
David Greenman 1995-03-23 09:43:40 +00:00
parent 567448c8c7
commit 64709e7406
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=7275
2 changed files with 2 additions and 8 deletions

View File

@ -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 @@ nfs_fsync(ap)
}
}
if (vp->v_dirtyblkhd.lh_first) {
#ifdef DIAGNOSTIC
vprint("nfs_fsync: dirty", vp);
#endif
goto loop;
}
}

View File

@ -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 @@ nfs_fsync(ap)
}
}
if (vp->v_dirtyblkhd.lh_first) {
#ifdef DIAGNOSTIC
vprint("nfs_fsync: dirty", vp);
#endif
goto loop;
}
}