Linux-kernel mailing list archive 1999-37,: Re: ext2 file sizes

# Re: ext2 file sizes

david parsons (o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s)
15 Sep 1999 13:34:04 -0700

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Trond Myklebust: "Re: NFS corruption revisited"
- Previous message: Alex Butcher: "[PATCH GOOD] RDSK patch works on Little-Endian - how about M68K?"
- Maybe in reply to: Blankenship, Keith: "ext2 file sizes"
- Next in thread: (no name): "Re: ext2 file sizes"

In article <linux.kernel.Pine.LNX.3.95.990915150738.775A-100000@chaos.analogic.com>,
Richard B. Johnson <root@chaos.analogic.com> wrote:
>On Wed, 15 Sep 1999, Blankenship, Keith wrote:
>
>> I am having some difficulty with the ext2 file systems. I need to generate a
>> file that will be > 5 Gigabytes, and there appears to be a file size cap at
>> approximately 2 Gig. I am running what appears to be a version 2.0.36
>> Kernel. Is there anything I can adjust, or do to increase the maximum file
>> size? Or is there a newer kernel that may work?
>>
>
>Note that on a 32-bit machine, toff_t, used as fpos_t, for file offsets,
>i.e., lseek, is unsigned 32 bits. You will not be able to access such a
>file on a 32-bit machine.

Sure you will; either via the traditional start-at-the-front and
read 'til you're finished method, or relative lseek, or llseek.

____
david parsons \bi/ relative seek is a pretty old method.
\/

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

- Next message: Trond Myklebust: "Re: NFS corruption revisited"
- Previous message: Alex Butcher: "[PATCH GOOD] RDSK patch works on Little-Endian - how about M68K?"
- Maybe in reply to: Blankenship, Keith: "ext2 file sizes"
- Next in thread: (no name): "Re: ext2 file sizes"