Re: ready for release of coreutils-8.11?

[Pádraig Brady]

On 11/04/11 21:09, Jim Meyering wrote:
> I've run the test suite on F15 x86_64 using each of ext3, ext4, btrfs and xfs.
> All tests passed on the first three FS types.
> On xfs there was only one failure: cp/sparse-fiemap.
> I pared it down to this stand-alone reproducer:
> 
>     rm -f j1 j2
>     perl \
>       -e 'BEGIN{$n=7*1024; *F=*STDOUT}' \
>       -e 'for (1..21) { sysseek (*F, $n, 1)' \
>       -e '&& syswrite (*F, chr($_)x$n) or die "$!"}' > j1
>     cp --sparse=always j1 j2
>     diff -u <(filefrag -v j1) <(filefrag -vs j2)
> 
> Here's the output.
> The difference that triggers the test failure is
> the fact that the "length" numbers differ:
> 
>     --- /proc/self/fd/11    2011-04-11 22:01:00.932737472 +0200
>     +++ /proc/self/fd/12    2011-04-11 22:01:00.932737472 +0200
>     @@ -1,6 +1,6 @@
>      Filesystem type is: 58465342
>     -File size of j1 is 301056 (74 blocks, blocksize 4096)
>     +File size of j2 is 301056 (74 blocks, blocksize 4096)
>       ext logical physical expected length flags
>     -   0       1     7310              31
>     -   1      33     7342     7340     95 eof
>     -j1: 3 extents found
>     +   0       1     7469              31
>     +   1      33     7501     7499     63 eof
>     +j2: 3 extents found

Hmm, this is with 128K block sizes?
There is a 4K hole at the start of each block which seems a bit strange.
Why are "3 extents found" but only 2 listed?
The last extent seems too long in both cases,
but that at least wouldn't cause cp to corrupt a copy.

cheers,
Pádraig.

p.s. I'll s/2.6.38/2.6.39/ in that test