"Brian" == Brian Tao taob@risc.org writes:
On Tue, 19 Sep 2000, Bruce Sterling Woodcock wrote:
Try killing and restarting your lock daemon, rather than rebooting the server. I realize that what you're describing shouldn't rely on that, but it's something you might try (I used to see the same thing with gopher processes).
Yup, tried that already (with expected results from looking ata lock_dump on the Netapp)... no go. I haven't caught anything in the act of trying an open() on a "stuck" file yet, but I'm guessing that will hang too. The stat() that typically precedes an application opening the file does hang. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't"
Brian -
I typically stop and restart both statd and lockd when I see NFS problems such as you report. These two daemons are closely related.
Perhaps the best way to do this is:
% sh /etc/init.d/nfs.client stop % sh /etc/init.d/nfs.client start
You may also need to clean out /var/statmon (statd state files) in between the stop and start. I have not had to to this recently.
-- Quentin Fennessy Quentin.Fennessy@amd.com Voice: 512.602.3873 Pager: 512.622.6316