Re: nfs client kernel crash

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

In article <Pine.NEB.4.64.1606281328120.25929%6bone.informatik.uni-leipzig.de@localhost>,
 <6bone%6bone.informatik.uni-leipzig.de@localhost> wrote:
>
>In my opinion, the NFS client implementation is still faulty. In the last 
>days I have created and deleted a mirror of Scientific Linux for several 
>times. This is a very large tree. Some directories have up to 10,000 
>entries. In some experiments I tried to clear the tree recursively and got 
>some error messages like:
>
>rm -rf scientific/
>rm: scientific/50/i386/updates/security: Directory not empty
>rm: scientific/50/i386/updates: Directory not empty
>rm: scientific/50/i386: Directory not empty
>rm: scientific/50/x86_64/sites/Fermi/updates/security: Directory not empty
>rm: scientific/50/x86_64/sites/Fermi/updates: Directory not empty
>rm: scientific/50/x86_64/sites/Fermi: Directory not empty
>rm: scientific/50/x86_64/sites: Directory not empty
>rm: scientific/50/x86_64: Directory not empty
>rm: scientific/50: Directory not empty
>rm: scientific: Directory not empty
>
>A new 'rm -rf' call deletes the remaining data. This behavior occurs 
>randomly. Often in a directory with many files. I observed the behavior
>with different nfs servers.
>
>I have not found any way to reproduce the behavior safely and with little 
>effort :-(

Well, there are two suspects for this, one is the directory cookie code and
the other is the silly rename files.

christos