From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Whoop Whouzer <tiredandnumb@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"Muntz, Daniel" <Dan.Muntz@netapp.com>,
Peter Chacko <peterchacko35@gmail.com>,
linux-nfs@vger.kernel.org
Subject: Re: nfs client performance while server is down
Date: Wed, 27 Jan 2010 13:40:03 -0500 [thread overview]
Message-ID: <1264617603.3788.77.camel@localhost> (raw)
In-Reply-To: <4B608492.2020702@oracle.com>
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
next prev parent reply other threads:[~2010-01-27 18:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 15:45 nfs client performance while server is down Whoop Whouzer
[not found] ` <d7f0b3a81001230745h18dbb14fi42f28adff0c45294-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-23 15:57 ` Peter Chacko
2010-01-23 16:27 ` Whoop Whouzer
[not found] ` <d7f0b3a81001230827y52727993nf60210ae610643b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-24 21:34 ` Muntz, Daniel
[not found] ` <7A24DF798E223B4C9864E8F92E8C93EC0527810C-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2010-01-24 22:03 ` Whoop Whouzer
2010-01-25 0:09 ` Whoop Whouzer
2010-01-25 16:48 ` Chuck Lever
2010-01-25 19:02 ` Whoop Whouzer
[not found] ` <d7f0b3a81001251102p5e631706jfd9f147a00487061-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-25 19:08 ` Chuck Lever
[not found] ` <d7f0b3a81001251138h30e25428o25db9bc8c0884636@mail.gmail.com>
[not found] ` <d7f0b3a81001251138h30e25428o25db9bc8c0884636-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-25 19:48 ` Whoop Whouzer
2010-01-25 21:01 ` Chuck Lever
2010-01-25 21:18 ` Whoop Whouzer
[not found] ` <d7f0b3a81001251318k42de9be2qe54f83bbd86cabb8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-25 21:26 ` Chuck Lever
2010-01-25 23:03 ` Whoop Whouzer
2010-01-26 23:21 ` J. Bruce Fields
2010-01-27 0:40 ` Whoop Whouzer
2010-01-27 17:10 ` J. Bruce Fields
2010-01-27 18:23 ` Chuck Lever
2010-01-27 18:40 ` Trond Myklebust [this message]
2010-01-27 18:47 ` Whoop Whouzer
2010-01-27 19:09 ` Trond Myklebust
2010-01-27 19:25 ` Whoop Whouzer
2010-01-27 19:30 ` Ray Van Dolson
2010-01-27 19:31 ` Peter Staubach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1264617603.3788.77.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=Dan.Muntz@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=peterchacko35@gmail.com \
--cc=tiredandnumb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox