Hello ML,
if I try to unmount a NFS-mounted directory my system freezes.
There is neither a error message nor a log entry.
I can't type anymore, but the NUM-Lock LED can still be switched
on/off. The host is also not ping-able.
I also tried different mount options (nfsvers=3, nfsvers=2, default or
even my former 2.4.x settings).
The NFS server is a 2.4.20 machine exporting with rw,async.
The client is using 2.5.71 (same with 2.5.70-mm9).
I'm sorry that I can't give you a more detailed description of the
problem. Perhaps you can give me some hints how to debug this.
TIA
Florian Huber
On Mon, 2003-06-16 at 22:45, Florian Huber wrote:
> if I try to unmount a NFS-mounted directory my system freezes.
> There is neither a error message nor a log entry.
>
> I can't type anymore, but the NUM-Lock LED can still be switched
> on/off. The host is also not ping-able.
>
> I also tried different mount options (nfsvers=3, nfsvers=2, default or
> even my former 2.4.x settings).
>
> The NFS server is a 2.4.20 machine exporting with rw,async.
> The client is using 2.5.71 (same with 2.5.70-mm9).
>
> I'm sorry that I can't give you a more detailed description of the
> problem. Perhaps you can give me some hints how to debug this.
Can you try to reproduce this from the console? I've seen this behavior
on previous versions of the kernel, and also the related kernel panic on
the console. It would be interesting if you could gather the OOPS
message and attach it in a message.
I would also suggest trying the following patch if you can:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.71/2.5.71-mm1/broken-out/rpc-depopulate-fix.patch
Or else, the latest 2.5.71-bk snapshot to see if it's fixed. At least,
I've been unable to reproduce previous NFS crashes on 2.5.71-mm1.