From: Joe Frost <joef@pixar.com>
To: linux-nfs@vger.kernel.org
Subject: Mounstats keying on fsid or ipaddr?
Date: Mon, 27 Jun 2011 11:15:26 -0700 [thread overview]
Message-ID: <4E08C8BE.2000407@pixar.com> (raw)
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?
Below are some relevant configuration files:
Automount configuration for path /shows/movie/$key
ribcage -rw,intr,rsize=131072,wsize=524288,tcp
primary.carrots:/ifs/shows/movie/ribcage
convert -rw,intr,rsize=131072,wsize=524288,tcp
primary.carrots:/ifs/shows/movie/convert
shottmp -rw,intr,rsize=131072,wsize=524288,tcp
primary.carrots:/ifs/shows/movie/shottmp
Proc/mounts on a particular server:
primary.carrots:/ifs/shows/movie/shottmp on /shows/movie/shottmp type
nfs
(rw,noatime,intr,tcp,intr,rsize=131072,wsize=524288,tcp,sloppy,addr=10.73.6.89)
primary.carrots:/ifs/shows/movie/ribcage on /shows/movie/ribcage type
nfs
(rw,noatime,intr,tcp,intr,rsize=131072,wsize=524288,tcp,sloppy,addr=10.73.6.89)
primary.carrots:/ifs/shows/movie/convert on /shows/movie/convert type
nfs
(rw,noatime,intr,tcp,intr,rsize=131072,wsize=524288,tcp,sloppy,addr=10.73.6.89)
We're using Isilon as the filer:
carrots-1# isi nfs exports list
Rule ID Paths Comment
11 /ifs/shows/brave/convert convert
16 /ifs/shows/movie/ribcage ribcage
17 /ifs/shows/movie/shottmp shottmp
next reply other threads:[~2011-06-27 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 18:15 Joe Frost [this message]
2011-06-27 18:41 ` Mounstats keying on fsid or ipaddr? Trond Myklebust
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=4E08C8BE.2000407@pixar.com \
--to=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).