What machine connected to particular nfsd?
Eric Anderson
anderson at centtech.com
Wed Apr 12 17:39:18 UTC 2006
Francisco Reyes wrote:
> I had an nfsd proces which was using up all the I/O the machine could
> handle. I could kill it, but another nfsd will again will just pickup
> the process.
>
> I am basically trying to tie up the process ID from ps/top to a
> particular machine connecting to that particular nfsd daemon.
>
> So.. figure I start out in top, then "m" to view I/O, then o "total" to
> sort..
>
> I see an nfsd with let's say a process ID (PID) 419 doing hundreds of
> transactions per second.. and vmstat "b" column shows the HDs are
> falling behind with nearly 200 transactions pending.. I now want to find
> what machine is connected to the nfsd with PID 419
>
> My guess is that a program was having problems and was doing lots of
> transactions... at the client.. problem is that I don't know which
> client machine.
>
> I tried tcpdump, but that pretty much showed me all the nfs clients. :-(
>
> Anyone else with NFS servers have had to deal with a rogue client? In
> particular finding out which client it is.
>
> Running FreeBSD 6 Stable as of early january 06.
Usually, a tcpdump tells me what I need to know. Usually a spinning
nfsd from a client is easily spotted in tcpdump.
I think, that since nfsd is using the kernel for all the file opens and
such, that you won't get a good list of which files are open by whom,
because the kernel owns them. I'm not sure if there is a way to find
that information.
Eric
--
------------------------------------------------------------------------
Eric Anderson Sr. Systems Administrator Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------
More information about the freebsd-isp
mailing list