I have an aix 5.2 machine that exports one directory to everyone in ro mode.
I occasionally get problems where client mount requests just
hang with no response, rebooting the server solves the problem for a short period of time but then it returns.
The problem disappeared for months, but has just returned.
On rebooting the server I noticed that the rpc.lockd was failing, and if I do a: lssrc -g nfs then rpc.lockd is shown as inoperative. I don't know if this has anything to do with my problem but was wondering if anyone might have any insight into why it might fail. If I try and start it manually here is what I get:.
# startsrc -s lockd
/usr/sbin/rpc.lockd -[t timeout] [-g grace_period] [-d debug]
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 16834.
# /usr/sbin/rpc.lockd -[t timeout] [-g grace_period] [-d debug]
/usr/sbin/rpc.lockd -[t timeout] [-g grace_period] [-d debug]
It would seem to be getting started with the "-d 0" parameter...
Thanks for any help:
--
db
I occasionally get problems where client mount requests just
hang with no response, rebooting the server solves the problem for a short period of time but then it returns.
The problem disappeared for months, but has just returned.
On rebooting the server I noticed that the rpc.lockd was failing, and if I do a: lssrc -g nfs then rpc.lockd is shown as inoperative. I don't know if this has anything to do with my problem but was wondering if anyone might have any insight into why it might fail. If I try and start it manually here is what I get:.
# startsrc -s lockd
/usr/sbin/rpc.lockd -[t timeout] [-g grace_period] [-d debug]
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 16834.
# /usr/sbin/rpc.lockd -[t timeout] [-g grace_period] [-d debug]
/usr/sbin/rpc.lockd -[t timeout] [-g grace_period] [-d debug]
It would seem to be getting started with the "-d 0" parameter...
Thanks for any help:
--
db