On 11/28/2011 10:41 AM, tao.peng@xxxxxxx wrote:
> Just out of curiosity, how is it going to work with sparse files? By default, cp uses --sparse=auto. And for sparse files, it avoids some disk allocation automatically. With fallocate(), do you plan to change the semantics?
With sparse files, coreutils currently uses fiemap (with a sync),
and thus has full details of what is sparse or empty etc.
So as detailed¹ on the coreutils list, the conversions would be:
--sparse=auto => 'Empty' -> 'Empty'
--sparse=always => 'Empty' -> 'Hole'
--sparse=never => 'Hole' -> 'Empty'
cheers,
Pádraig.
¹ http://debbugs.gnu.org/9500#14
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
