From: "Lever, Charles" <cel@netapp.com>
Subject: RE: sendmail "cannot fsync directory" after 2.4 -> 2.6
Date: Thu, 9 Sep 2004 11:54:23 -0700
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <482A3FA0050D21419C269D13989C61130435E7A8@lavender-fe.eng.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Cc: <nfs@lists.sourceforge.net>
To: "Ara.T.Howard" <Ara.T.Howard@noaa.gov>
Errors-To: nfs-admin@lists.sourceforge.net

> > Yep. We forgot to add the stub to Linux 2.6.x. Please=20
> confirm that the=20
> > following patch fixes the problem for you.
>=20
> will fsync'ing a directory have any affect on the client=20
> inode cache for that dir?  eg. will it invalidate that cache?

ara-

looking at the patch trond posted, it appears to add a "no-op" function
for fsyncing NFS directories.  this means fsync against an NFS directory
will not complain, but otherwise does nothing.


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs