bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: rm -r sometimes produces errors under NFS


From: Jim Meyering
Subject: Re: rm -r sometimes produces errors under NFS
Date: Mon, 05 Mar 2007 17:36:08 +0100

Vincent Lefevre <address@hidden> wrote:
> On 2007-03-05 16:45:46 +0100, Jim Meyering wrote:
>> Thanks for the report.
>>
>> What version of coreutils are you using?
>
> rm (GNU coreutils) 5.97
>
> This is the version from Debian/testing.
>
>> From the output, I'll bet it is not new.
>>
>> Can you reproduce the problem using the latest snapshot?
>>
>>   http://meyering.net/cu/coreutils-6.8+.tar.gz
>
> Tried, and this is even worse: I got the error for *every* file:

Maybe it's actually better :-)
More consistent.

> courge:~/software>  \rm -r zsh-4.3.2
> [...]
> rm: cannot remove `zsh-4.3.2/Functions/Example/randline': No such file or 
> directory
> rm: cannot remove `zsh-4.3.2/Functions/Example/zls': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/completion-style-guide': No such file or 
> directory
> rm: cannot remove `zsh-4.3.2/Etc/zsh-development-guide': No such file or 
> directory
> rm: cannot remove `zsh-4.3.2/Etc/.cvsignore': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/ChangeLog-3.1': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/ChangeLog-3.0': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/FTP-README': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/STD-TODO': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/CONTRIBUTORS': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/ChangeLog-4.1': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/changelog2html.pl': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/Makefile.in': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/.distfiles': No such file or directory
> rm: cannot remove `zsh-4.3.2/Etc/FAQ': No such file or directory
> zsh: exit 130
>
> (interrupted by Ctrl-C). Reproduced 3 times (out of 3) when zsh-4.3.2
> was created on another machine[*], whereas the old rm (/bin/rm) doesn't
> have this problem under the same conditions.
>
> [*] doublejack (so that I can remember).

Thanks.
So please tell us about your systems.
OS on the client, and OS on the server?

Also, it'd be nice if you could produce a small test case
that would still demonstrate the failure.

Please run strace -o log rm -r small-test-dir
and put the log somewhere public -- or even send it if it's not too big.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]