Mounstats keying on fsid or ipaddr?
Subsystems (2)
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 shottmpQuoted 6 lines · Joe Frost
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
Signature · 6 lines
Trond Myklebust Linux NFS client maintainer NetApp [email protected] www.netapp.com