In article <pine.neb.4.64.1606171144540.25...@6bone.informatik.uni-leipzig.de>, <6b...@6bone.informatik.uni-leipzig.de> wrote: >On Tue, 14 Jun 2016, Christos Zoulas wrote: > >> On Jun 14, 2:07pm, 6b...@6bone.informatik.uni-leipzig.de >(6b...@6bone.informatik.uni-leipzig.de) wrote: >> -- Subject: Re: nfs client kernel crash >> >> | On Tue, 14 Jun 2016, Christos Zoulas wrote: >> | >> | > Yes, that helps. No crash though? >> | >> | So far, no crash. But this often takes several days. >> >> Ok. Let's take a look at the EINTR issue then. >> >> christos >> >First the good news. The patch seems to help! Since applying the patch I >could not see any more crash. Can you apply the patch to current and >netbsd-7?
Yes, I have. I will ask for a pullup. >messages. In some cases occurs an nfs i/o error at the same time. >Unfortunately the printf statement is not executed, so the problem must >occur at a different location. That's good and bad. It is good because it would be hard to do a retry there, it is bad because we don't know yet where it is. I would start adding more printfs. You are not mounting with "intr" I hope, are you? christos
