Summary: | nfs: server nfs0 not responding, timed out, only on 2.4.22 kernels | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Guy Van Sanden <nocturn> |
Component: | [OLD] Core system | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | VERIFIED FIXED | ||
Severity: | major | CC: | net-fs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Kernel config file |
Description
Guy Van Sanden
2004-01-16 06:20:18 UTC
Some additional info. This error only occurs very infrequent on small operations (openign mbox file, writing documents). Yet multiple heavy operations (search through 100MB mail archive, tar operations), specially concurrently, always give errors and sometimes the operation fails. Can you attach your .config, which version of nfs you are using, any other mount options you have for the nfs fs, and the os/kernel of the nfs server itself. Just so you know, I'm unable to reproduce this here, so you may have to do a little hunting for us. Created attachment 23932 [details]
Kernel config file
These are the fstab mount options: nfs0:/data/home /home nfs soft,rsize=8192,wsize=8192,nolock,nosuid 0 0 nfs0:/data/export /netdata nfs soft,rsize=8192,wsize=8192,nolock,nosuid 0 0 The nolock is to keep Ximian Evolution happy. NFS version is 3 There are no special options set on the server. Kernel 2.4.21 (on Mandrake) is OK 2.4.20-r8 on Gentoo is OK I am using an integrated NIC (ECS K7S5A MB with Sis 735 chipset) I just ran some test against a Linux nfs server (Mandrake 9.1), and it gave me the same error, so we can rule out the server. I don't get it... Still it is considerably better in -r5 then -r4. I also tried running without the wsize and rsize = no change using a hard nfs mount still gives the error, but apps seem to survive better. latest gs-sources (2.4.23) do not have this problem, I'm compiling vanilla to test now vanilla 2.4.24 is fine gs-sources is my current kernel for now Found working kernel. Bug fixed. Bug closed. Upgrade of kernel straightened things out. |