Re: nfs client kernel crash

[christos%zoulas.com@localhost (Christos Zoulas)]

On Jun 14, 12:41pm, 6bone%6bone.informatik.uni-leipzig.de@localhost (6bone%6bone.informatik.uni-leipzig.de@localhost) wrote:
-- Subject: Re: nfs client kernel crash

| On Tue, 14 Jun 2016, 6bone%6bone.informatik.uni-leipzig.de@localhost wrote:
| 
| > I applied the patch. For testing I have started a "rm -rf" on a large 
| > directory tree. dmesg reports:
| >
| > nfs server 172.18.86.13:/vol/vol_bsd_2: is alive again
| > nfs server 172.18.86.13:/vol/vol_bsd_2: not responding
| > nfs server 172.18.86.13:/vol/vol_bsd_2: not responding
| > nfs server 172.18.86.13:/vol/vol_bsd_2: not responding
| > nfs server 172.18.86.13:/vol/vol_bsd_2: not responding
| > nfs server 172.18.86.13:/vol/vol_bsd_2: is alive again
| > nfs server 172.18.86.13:/vol/vol_bsd_2: not responding
| > nfs server 172.18.86.13:/vol/vol_bsd_2: is alive again
| > ...
| >
| 
| If it helps: 'rm -rf' reports randomly "Interrupted system call"

I think it is this:

        while ((error = nfs_connect(nmp, rep, &lwp0)) != 0) {
                if (error == EINTR || error == ERESTART)
                        return (EINTR);
                kpause("nfscn2", false, hz, NULL);
        }


Can you put a printf to verify?

christos