GNU bug report logs - #9500
cp: use posix_fallocate where supported

Previous Next

Full log

Message #41 received at 9500 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Pádraig Brady <P <at> draigBrady.com>
Cc: 9500 <at> debbugs.gnu.org, Kelly Anderson <kelly <at> silka.with-linux.com>,
	Goswin von Brederlow <goswin-v-b <at> web.de>
Subject: Re: bug#9500: [PATCH]: use posix_fallocate where supported
Date: Tue, 29 Nov 2011 14:22:33 +0100

Pádraig Brady wrote:
> On 11/25/2011 10:59 AM, Pádraig Brady wrote:
>> On 11/25/2011 10:13 AM, Pádraig Brady wrote:
>>
>>> Hmm, one of your points above got me thinking.
>>> Might fallocate() fail to allocate an extent with ENOSPC,
>>> but there could be fragmented space available to write()?
>>> That would scupper benefit (2) above :(
>>> I'll ask linux-fsdevel <at> vger.kernel.org
>>
>> And the response from there is that fallocate() will
>> check the free blocks first, and then try to allocate
>> as a contiguous extent, but that part is not guaranteed.
>> So we still get benefit (2).
>
> However that thread has continued, and it
> was mentioned that benefit (1) might actually
> be detrimental, at least for small files.
>
> http://thread.gmane.org/gmane.linux.file-systems/59092

Sigh, indeed.
Do you think it's even worth an option, now?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.