From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Joe Frost <joef@pixar.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Mounstats keying on fsid or ipaddr?
Date: Mon, 27 Jun 2011 14:41:36 -0400 [thread overview]
Message-ID: <1309200096.25643.10.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4E08C8BE.2000407@pixar.com>
On Mon, 2011-06-27 at 11:15 -0700, Joe Frost wrote:
> We've been using mountstats to graph/track NFS usage based on path.
> We've recently made some changes on how we mount filesystems here where
> it's possible the same IP will be used for multiple mounts. Since that
> we've noticed that all mounts to the same IPaddr are showing the same
> statistics. Wondering if anyone had ideas why it might be keying off of
> IPaddr?
mountstats keys off the fsid as reported on the _server_. If your server
is reporting that these directories are all contained in one big volume,
then that will suffice to confuse the client.
One way to work around this, is to tell the client that the
subdirectories are on different volumes. You can do that using the
"nosharecache" mount option. Beware, however, that if you have hard
linked files that appear under more than one of these mountpoints, then
the client will treat them as if they are completely separate files for
the purposes of caching and close-to-open cache consistency checking.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2011-06-27 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 18:15 Mounstats keying on fsid or ipaddr? Joe Frost
2011-06-27 18:41 ` Trond Myklebust [this message]
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=1309200096.25643.10.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=joef@pixar.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).