NFS 4 client callback port

Talpey, Thomas Thomas.Talpey at netapp.com
Thu Jun 12 09:03:43 EDT 2008


By the way, you might want to try turning on nfs callback
debugging, to see if any of the dprintk's in fs/nfs/callback.c
are being triggered:

	rpcdebug -m nfs -s callback

The port number is printed when created "Callback port = 0x%x"...
It will also emit a line each time the server calls back to it.

Tom.

At 08:52 AM 6/12/2008, Talpey, Thomas wrote:
>At 08:47 AM 6/12/2008, Guillaume Rousse wrote:
>>I got only one, that's correct:
>>[root at chatelet ~]# ps ax | grep nfsv4-svc
>>  7146 ?        S      0:00 [nfsv4-svc]
>
>I think this is sufficient evidence that the ports you are seeing are not
>NFSv4 callback ports. Do you see the port count rise as you do nfs4
>mounts manually?
>
>>My point is: if ps can identify kernel processes, why can't netstat ?
>
>Beats me!
>
>Tom.
>
>_______________________________________________
>NFSv4 mailing list
>NFSv4 at linux-nfs.org
>http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4



More information about the NFSv4 mailing list