jeff.liu wrote:
> Sunil Mushran wrote:
>> On 06/10/2010 04:47 PM, Paul Eggert wrote:
>>> On 06/09/2010 11:56 PM, jeff.liu wrote:
>>>
Yeah, I just realized that the behaviour I observed is caused by the
delay allocation mechanism of
the particular FS.
>>> If the file sys
Jim Meyering wrote:
> Eric Sandeen wrote:
> ...
>> I suppose it would be nice to at least make that last buffered IO
>> synchronous if possible, or sync the file afterwards.
>> POSIX_FADV_DONTNEED for extra credit? :)
>
> Good idea.
> What do you think of this?
Eric Sandeen wrote:
> Jim Meyering wrote:
...
>> diff --git a/doc/coreutils.texi b/doc/coreutils.texi
>> index acec76e..6fa2602 100644
>> --- a/doc/coreutils.texi
>> +++ b/doc/coreutils.texi
>> @@ -7861,6 +7861,10 @@ dd invocation
>> @opindex direct
>&g
Jim Meyering wrote:
> Eric Sandeen mentioned that dd's O_DIRECT-exposing code
> didn't always work. The problem is that the kernel imposes
> draconian restrictions on the size of buffer that one may
> write to an FD opened with O_DIRECT. Currently, at least on
> ext
Giuseppe Scrivano wrote:
> Hello,
>
> Pádraig Brady writes:
>
>> Tilman Schmidt wrote:
...
>>> Why not make it, in the best Unix tradition, a single
>>> executable whose action depends on the name it is run as?
>> Hmm. Good idea.
>> There is precedent for that already in coreutils.
>
> What d
Pádraig Brady wrote:
> Eric Sandeen wrote:
>> Pádraig Brady wrote:
>>> Eric Sandeen wrote:
>>>> TBH I think "truncate --allocate" sounds a little odd. (Now that I
>>>> think back, I think I mentioned this before). truncate(1) and
>>>&
Pádraig Brady wrote:
...
> On a related note it looks like fallocate64() which is required
> on 32 bit systems will not be supported in glibc-2.10 as it
> was released as a glibc-2.11 symbol. That means that 32 bit `cp`
> built on glibc-2.10 will not allocate extents for a file,
> and likewise 32
Jim Meyering wrote:
> Eric Sandeen wrote:
>> Jim Meyering wrote:
>>> In http://bugzilla.redhat.com/485507
>>>
>>> Eric Sandeen proposed to add ext4 to the list of names
>>> currently reported for that type of file system ("ext2/ext3").
>&g
Jim Meyering wrote:
> In http://bugzilla.redhat.com/485507
>
> Eric Sandeen proposed to add ext4 to the list of names
> currently reported for that type of file system ("ext2/ext3").
>
> I'm reluctant to change that string, because doing so might
>
