Date: Mon, 30 May 2011 22:17:48 -0400 From: Mark Saad <nonesuch@longcount.org> To: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Mount_nfs question Message-ID: <BANLkTi=897zHk3mcHg35T-rJdPRe2n_8-Q@mail.gmail.com> In-Reply-To: <1385828099.1028129.1306800800853.JavaMail.root@erie.cs.uoguelph.ca> References: <BANLkTimwQbfWyLF6gvp-PsWtx38s33b9ZQ@mail.gmail.com> <1385828099.1028129.1306800800853.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 30, 2011 at 8:13 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote: >> Hello All >> So I am stumped on this one. I want to know what the IP of each >> nfs server that is providing each nfs export. I am running 7.4-RELEASE >> When I run "mount -t nfs" I see something like this >> >> VIP-01:/export/source on /mnt/src >> VIP-02:/export/target on /mnt/target >> VIP-01:/export/logs on /mnt/logs >> VIP-02:/export/package on /mnt/pkg >> >> The issue is I use a load balanced nfs server , from isilon. So VIP-01 >> could be any one of a group of IPs . I am trying to track down a >> network congestion issue and I cant find a way to match the output of >> lsof , and netstat to the output of mount -t nfs . Does anyone have >> any ideas how I could track this down , is there a way to run mount >> and have it show the IP and not the name of the source server ? >> > Just fire up wireshark (or tcpdump) and watch the traffic. tcpdump > doesn't know much about NFS, but if al you want are the IP#s, it'll do. > > But, no, mount won't tell you more than what the argument looked like. > > rick > Wireshark seams like using a tank to swap a fly. -- mark saad | nonesuch@longcount.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=897zHk3mcHg35T-rJdPRe2n_8-Q>