xfs
[Top] [All Lists]

Re: XFS weirdness <- GLibC, LFS and NFS ... oh my!

To: Jason Walker <unseen@xxxxxxxxx>
Subject: Re: XFS weirdness <- GLibC, LFS and NFS ... oh my!
From: Bryan-TheBS-Smith <thebs@xxxxxxxxxxx>
Date: Wed, 28 Feb 2001 15:26:28 -0500
Cc: Sean Dougherty <sean@xxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
Organization: (Personal)
References: <Pine.LNX.4.10.10102281453120.10899-100000@xxxxxxxxxxxxxxxxxxx>
Reply-to: thebs@xxxxxxxxxxx, b.j.smith@xxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Jason Walker wrote:
> Just a little FYI, EXT2 does not have a 2GB file size limit on 2.4.x
> kernels.  Perhaps trying the same thing with ext2 would help determine the
> problem.  I didn't beleive it when people said I coudl make larger files on
> ext2, so I tried it myself. and indeed, they were right! I hope this help
> you figure out the real source of the problem.

It's known as LFS (large file support).  It is a workaround for
POSIX UNIX systems (meaning it affects other platforms than just
Linux) on 32-bit processors (so there are NO issues on Linux/Alpha,
SPARC64, etc...).

>From my understanding, LFS support on Linux requires:

Local:
   Kernel 2.4.x  (or LFS kernel 2.2.x backport + filesystem w/LFS)
   GLibC 2.2.x
   Utility/App:  Linked against GLibC 2.2.x

Remote via NFS:
   Kernel 2.4.x  (or LFS 2.2.x backport)
   kNFSd 2.4.x   (or NFS v3 2.2.x backport w/LFS patch)
   Client:  64-bit platform or 32-bit/LFS-linked LibC/utils

I have kernel 2.2.x systems with Ext3+LFS & NFS3+LFS applied that
allows my Solaris clients to create >2GB files (even though the
local Linux utilities are GLibC 2.1.x and cannot).

As such, in this gentleman's case, I concur that he should try
creating the file via his NFS client only to an Ext2-exported
filesystem.  It could be the utilities on his client.

-- 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>