[nycbug-talk] What client connected to nfsd?

Marc Spitzer mspitzer at gmail.com
Sat Apr 15 15:55:52 EDT 2006

On 4/15/06, Francisco Reyes <lists at stringsutils.com> wrote:
> Bjorn Nelson writes:
> > lsof -i
> > will show you daemons to ip:socket
> Doesn't seem to help much with nfs.
> lsof -i | egrep -i "nfsd|2049|<IP>"
> nfsd  415  root  3u  IPv4 0xc7eb81cc 0t0  TCP *:nfsd (LISTEN)

You may be trying to be too efficent.  Run lsof -i or sockstat and
dump the output to a text file and look at it with more and see what
you see.  then figure out how to grep for it.

Lets look at this logicly, to solv this you need two peices of information:
1: a mapping of nfsd's to ip addresses
2: traffic summeries to see who is beating up your server

1: lsof/sockstat
2: tcpdump + script to sumerize or look in ports for something that
will summerize for you, bpgt might do that

a process that is doing this will hang around for a while.


> 2049 is the port nfsd uses.
> I have several machines connected to that nfs server doing work and the line
> above was the only thing returned.
> > You can filter tcpdump by ip (on nfs server):
> > tcpdump src clientip
> :-)
> If I knew the machine I wouldn't have a problem.
> That is what I am trying to determine.
> What machine/IP is connected to a particular nfsd process.
> _______________________________________________
> % NYC*BUG talk mailing list
> http://lists.nycbug.org/mailman/listinfo/talk
> %Be sure to check out our Jobs and NYCBUG-announce lists
> %We meet the first Wednesday of the month

"We trained very hard, but it seemed that every time we were beginning to
form into teams we would be reorganized. I was to learn later in life that
we tend to meet any new situation by reorganizing, and a wonderful method it
can be for creating the illusion of progress, while producing confusion,
inefficiency and demoralization."
-Gaius Petronius, 1st Century AD

More information about the talk mailing list