GNU bug report logs - #12626
Bug?: dd limited to <2G read size (2G-8K) on 64 bit machine?

Previous Next

Package: coreutils;

Reported by: Linda Walsh <coreutils <at> tlinx.org>

Date: Fri, 12 Oct 2012 03:13:02 UTC

Severity: normal

Done: Pádraig Brady <P <at> draigBrady.com>

Bug is archived. No further changes may be made.

Full log


Message #28 received at 12626-done <at> debbugs.gnu.org (full text, mbox):

From: Linda Walsh <coreutils <at> tlinx.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Pádraig Brady <P <at> draigBrady.com>, 12626-done <at> debbugs.gnu.org
Subject: Re: bug#12626: Bug?: dd limited to <2G read size (2G-8K) on 64 bit
	machine?
Date: Fri, 12 Oct 2012 08:14:37 -0700
[Message part 1 (text/plain, inline)]
I was writing to /dev/null.  It doesn't seem to have an issue.

This appears to be related to "iflag=direct" more than anything.

W/o direct it works, but, for example I can't use iflag=direct with 
/dev/zero
for even a 4K block size.

Hmmm....




Paul Eggert wrote:
> On 10/12/2012 02:14 AM, Pádraig Brady wrote:
>   
>> if you specify ibs and obs seperately,
>> then you will get writes of the size you requested at least.
>>     
>
> Won't there be similar problems with the write system
> call too?  Perhaps not on Linda's system, but on other
> systems.  Once the buffer size exceeds 2 GB or so,
> things get pretty dicey in the wild, not due to any
> problem in dd itself, but due to the kernels or
> file systems that dd relies on.
>   
[Message part 2 (text/html, inline)]

This bug report was last modified 12 years and 224 days ago.

Previous Next


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