[EMAIL PROTECTED] (Bob Proulx) wrote:
> Bob Proulx wrote:
>> Yes, both an error but different errors. Can you reproduce the error
>> from the command line? It would probably make further debugging
>> easier.
>
> I was able to find an ia64 machine running an old 2.4.19 kernel. Not
> quite the same but I was able to reproduce the problem there.
>
>> mkdir -p a/t b/t
>> touch a/t/f
>> strace -e file $builddir/src/mv b/t a
>
> rename("b/t", "a/t") = -1 ENOTEMPTY (Directory not empty)
>
>> I think this problem will simply be one of kernel error message
>> differences in the different kernel versions.
>
> Yep.
>
>> That seems really strange. If I read that right it collapses to a
>> very simple thing that should not be failing.
>>
>> mkdir -p d/sub empty
>> $builddir/src/mv -fT d empty
>> strace -e file $builddir/src/mv -fT d empty
>
> Strace on linux-2.4.19 on an ext3 filesystem shows this:
>
> rename("d", "empty") = -1 ENOTEMPTY (Directory not empty)
>
> While on linux-2.6.12:
>
> rename("d", "empty") = 0
Hi Bob,
Thanks for investigating.
I don't think coreutils should try to work around this kernel/fs bug.
Do you know if this is fixed in later 2.4.x releases? I sure hope so.
_______________________________________________
Bug-coreutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-coreutils
