Pádraig Brady wrote:
I was looking at adding fallocate() to copy.c,
now that the fiemap code has gone in and
I noticed that if there was allocated space
at the end of a file, not accounted for
in st_size, then any holes would not be detected.
Good point.
In what other cases does the sparse
Running make -j25 check on a nominal-12-core F14 system would
cause serious difficulty leading to an OOM kill -- and this is brand new.
It worked fine yesterday. I tracked it down to all of the make processes
working on the built_programs.list (in src/Makefile.am) rule
built_programs.list:
On Tuesday 08 February 2011, Jim Meyering wrote:
Chris Clayton wrote:
Firstly, please cc me on any reply because I'm not subscribed.
I'm trying to build coreutils-8.10 but am getting a failure when I run
make check.
The failure occurs in check cp/sparse-fiemap and the log of that
