Re: NFS file locking broken (take 2)
H. J. Lu (hjl@freya.yggdrasil.com)
Sun, 23 Aug 1998 00:42:40 -0700 (PDT)
>
> Alan had asked about repeatable bugs. The only ones that I've observed
> across multiple kernel versions (~2.1.7x through present) are:
>
> - Occasional file corruption and truncation when copying files from client
> to server. This is incredibly rare, and I've found no good way to
> reproduce it. Since it is never accompanied by error messages, I usually
> find out later when, e.g. attempts at unpacking a downloaded tarball fail
> with "tar archive truncated.." messages.
>
> n.b. Alan: The Ooops's didn't appear until 2.1.117, AFAIK. They have not
> been a longstanding issue.
>
> - More commonly, a mass 'cp -a' of the entire kernel source tree from
> server to client will result in one or more target directories being
> completely empty. Again, not easily reproducible and no error messages.
I am heavily depending on NFS. I haven't seen those myself. But my NFS
is patched by me.
>
> - When building the kernel on an NFS mounted directory, a 'make mrproper'
> will sometimes fail with numerous complaints about "files in use" when
> trying to remove the linux/include/config hierarchy. Usually, the second
> attempt succeeds.
How easy to reproduce it?
>
> I know this is not much to go on, but perhaps it may suggest a set of
> functions to instrument? Again, these are quite rare but have persisted
> over quite a number of kernel revs.
>
If I can reproduce it, I will take a look.
H.J.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html