xfs
[Top] [All Lists]

Re: 2GB filesize limit.

To: Chuck Rouillard <chuckr@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: 2GB filesize limit.
From: Bryan-TheBS-Smith <thebs@xxxxxxxxxxx>
Date: Fri, 02 Mar 2001 09:08:12 -0500
Cc: Linux - XFS <linux-xfs@xxxxxxxxxxx>
Organization: (Personal)
References: <Pine.BSF.4.31.0103011113230.40049-100000@opus.sandiegoca.ncr.com>
Reply-to: thebs@xxxxxxxxxxx, b.j.smith@xxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Chuck Rouillard wrote:
> 1. Does Linux/XFS break the 2G filesize limit (on the
>    assumption that certain support libraries exist and
>    correctly configured)?

XFS itself breaks the 2GB filesize limit.  I will assume, for a
moment, that the VFS in 2.4 has been changed to accomodate this with
LFS?

>    The linux-xfs.sg.com/projects/xfs/ page mentions
>    "(no more 2GB limits)" but it isn't clear what exactly
>    that refers to, nor if that claim is valid with Linux.

Good question.  I guess I need to dig into the source of XFS and
2.4's VFS to find out for sure.

As far as kernel 2.2, I seriously doubt it works without some
serious modification.  I got LFS to work on 2.2 kernels with Ext3
and NFS, but it took additional patches to not only the kernel, but
Ext3 and NFS parts of the kernel.

> 2. If the above is true, do userland tools such as `ls',
>    `cp', `mv', et cetera, need mending?

That's where GLibC comes in.

E.g., my RedHat 6.2 systems have only GLibC 2.1, so not really.  But
I can boot a 2.2 kernel with Ext3 and NFS, with LFS patches for all,
and my 64-bit Solaris/SPARC systems be able to write >2GB files to
it.  I can also back it up because I'm using "dump/restore"
(although tar/cpio/bru/etc... might have isues).

> 3. Has XFS support on Linux/IA-64 reached the mumbled
>    stage?

No idea.  Sorry.

-- TheBS


--
Bryan "TheBS" Smith          chat:thebs413 @AOL/MSN/Yahoo
Engineer      mailto:b.j.smith@xxxxxxxx,thebs@xxxxxxxxxxx
*********************************************************
"Never apply a Star Trek solution to a Babylon 5 problem"
                                    -- Nicholas C. Weaver

<Prev in Thread] Current Thread [Next in Thread>