Hi Daniel,
I do not believe this would be related. The problem I saw was ESTALE
being returned to programs using NFS V2 to access reiserfs filesystems,
after a server reboot. While rebooting the servers, the clients do
print the same syslog messages that you see because the server isn't
responding to client rpc messages. Your lockup on the server is the
cause of the messages on the clients.
When the lockup occurs does, "top" running on the server give you some
hint about what's happening? Is the system too locked up to see if "ps"
shows the nfsd threads all in disk wait, or, can you tell that the disks
are really busy? Are you able to type on the console or switch to the
console during the lockup?
Sorry, I don't think this fix well help.
Anne
Daniel wrote:
>
>
> Hi Anne, list,
> I've been having problems with 2.4.9 on an SMP box exporting NFS v2 on
> ReiserFS to a 2.2.16-3 box. Every hour (literaly once every hour 10-12
> minutes past(not a cron job either)) I get this on the client:
> Aug 29 12:12:27 www1 kernel: nfs: server 192.168.1.1 not responding,
> still trying
> Aug 29 12:12:31 www1 kernel: nfs: task 44914 can't get a request slot
> During this time the server completely locks up for about 30-60 secs,
> and then resumes like nothing happened. Is this related?
>
> Thanks,
>
> --
> --
> Daniel Bohling
> NewsFactor Network
