On Jun 14, 8:32am, [email protected] ([email protected]) wrote: -- Subject: Re: nfs client kernel crash
| On Mon, 13 Jun 2016, Christos Zoulas wrote: | | > Can you try this? The first one might not apply cleanly since I changed | > the loop, but it should work just the same if you put the spl stuff around | > the old loop. | | 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 | ... I've seen that too... | The behavior already exists prior apply the patch. I think that the | crash will also reoccur. | | The storage is a netapp nfs volume. The volume is only mounted at my | server. On the storage there are no load problems. Did it crash? christos
