Re: linux 2.3/4 and large files
- To: <debian-devel@lists.debian.org>
- Subject: Re: linux 2.3/4 and large files
- From: Joel Klecker <jk@espy.org>
- Date: Wed, 1 Dec 1999 07:22:57 -0800
- Message-id: <v04220809b46a49c19706@[206.163.71.146]>
- In-reply-to: <NDBBIHOCOLLJGPAMMIFPIEIEEAAA.katz@advanced.org>
- References: <NDBBIHOCOLLJGPAMMIFPIEIEEAAA.katz@advanced.org>
At 20:24 -0500 1999-11-30, Terry Katz wrote:
>I've been away from the list for a little while, and am not sure if this was
>brought up yet, if it was, I'm sorry ...
>
>Playing around with the latest unstable branch of the linux kernel today, I
>noticed a 'bug' (not really) in the standard include files (namely
>bits/types.h) and linux 2.3/4 .. __off_t is defined as a 'long int'
>(signed), making the max value 2147483647.. after ungzip'ing a log file,
>totaling 8gig (uncompressed), the file size showed up as 630meg or so using
>ls and stat directly (performing a head and tail on the log file, and the
>same log file on an irix box, showed that the entire file was indeeed
>there).. I know that even if off_t was unsigned, the max would only be
>4294967295 bytes (4gig)....
>
>Does anyone know if there are plans on fixing this? (i know this is not
>debian specific, just wondering if anyone knows...)
On 64-bit architectures, __off_t is a 64-bit signed number. On 32-bit
architectures, there is __off64_t.
The kernel support for 64-bit filesizes on 32-bit architectures is going
into or is already in Linux 2.3, and the libc support is there in glibc 2.1.
--
Joel Klecker (aka Espy) Debian GNU/Linux Developer
<URL:mailto:jk@espy.org> <URL:mailto:espy@debian.org>
<URL:http://web.espy.org/> <URL:http://www.debian.org/>
Reply to: