Subject: Re: Trouble with the filesize limit
From: Steven Newbury <steven.newbury1@ntlworld.com>
To: Eric Lammerts <eric@lammerts.org>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <1088649927.6630.21.camel@timescape.home.snewbury.org.uk>
References: <1088647102.6630.15.camel@timescape.home.snewbury.org.uk>
	 <Pine.LNX.4.58.0406302211490.21486@vivaldi.madbase.net>
	 <1088649927.6630.21.camel@timescape.home.snewbury.org.uk>
Content-Type: text/plain
Message-Id: <1088652347.6630.26.camel@timescape.home.snewbury.org.uk>
Mime-Version: 1.0
Date: Thu, 01 Jul 2004 04:25:48 +0100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1302
Lines: 35

On Thu, 2004-07-01 at 03:45, Steven Newbury wrote:
> Thanks for the quick response.
> 
> On Thu, 2004-07-01 at 03:21, Eric Lammerts wrote:
> > On Thu, 1 Jul 2004, Steven Newbury wrote:
> > > It isn't possible for me to download more than 2GiB.
> > 
> > > I've tried programs d4x, wget etc., each of them have received a
> > > SIGXFSZ and exited at 2GiB.
> > 
> > Probably none of those apps were compiled with
> > -D_FILE_OFFSET_BITS=64 ...
> > 
> Okay I've recompiled wget with -D_FILE_OFFSET_BITS=64.  Now I've got:
> get: progress.c:706: create_image: Assertion `insz <= dlsz' failed.
> when I try to continue the download...
This, I guess, is a bug in wget.  Are the various types like size_t set
correctly for FILE_OFFSET_BITS=64, or should special care be taken
within each app to ensure types of sufficient size are used?

> 
> > > Strangely I am able to create much larger files with dd.
> > 
> > That one probably is... (the coreutils configure script enables that
> > automatically)
> > 
> > Eric
-- 
Steven Newbury <steven.newbury1@ntlworld.com>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/