So? I don't see why that would be an NFS problem. As far as I can see from this thread, you are basically asking us to fix these broken applications by implementing a "disconnected NFS" mode. While that may indeed be a cool thing to support, I haven't seen anybody so far stepping up and saying that they have the time and resources to work on it. Are you volunteering? Trond On Wed, 2010-01-27 at 19:47 +0100, Whoop Whouzer wrote: > ok, but it's not just GNOME/nautilus behaviour. For one, I am > experiencing problems with just about all applications that require > (local) disk access. Furthermore, problems have also been reported > with xfce/thunar and also with KDE. > > A bug for this issue has just been created for xfce/thunar: > http://bugzilla.xfce.org/show_bug.cgi?id=6185 > > On Wed, Jan 27, 2010 at 7:40 PM, Trond Myklebust > <trond.myklebust@xxxxxxxxxx> wrote: > > On Wed, 2010-01-27 at 13:23 -0500, Chuck Lever wrote: > >> On 01/26/2010 06:21 PM, J. Bruce Fields wrote: > >> > I wonder if nautilus (or some library it uses) likes to regularly > >> > "statfs" all the filesystems it knows about? > >> > >> The NFS client seems to like to send these periodically, but I've never > >> looked into why. It's probably triggered by some cache timeout, and > >> gathers recent server file system information. > > > > No. It is entirely application driven. Furthermore, most of the statfs > > data is uncached, since it should not be performance critical in any > > sane application environment. > > > > IOW: I agree with Bruce that this is most likely GNOME or nautilus > > triggering statfs calls. Indeed, when I do actually open a window on > > some directory it also appears to display the free space. > > > > Trond > > > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
