xfs
[Top] [All Lists]

Re: Anyone know what this error means?

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: Anyone know what this error means?
From: Steve Lord <lord@xxxxxxx>
Date: 09 Jan 2002 12:20:45 -0600
Cc: Adam McKenna <adam-dated-1010968404.3db79f@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20020109190517.A19543@wotan.suse.de>
References: <20020109003323.GW4511@flounder.net> <1010588784.29727.30.camel@jen.americas.sgi.com> <20020109190517.A19543@wotan.suse.de>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Wed, 2002-01-09 at 12:05, Andi Kleen wrote:
> On Wed, Jan 09, 2002 at 09:06:24AM -0600, Steve Lord wrote:
> > > Anyone know what is going on here?
> > 
> > You are being bitten by O_LARGEFILE - the linux kernel now does not let
> > an application which does not open files with O_LARGEFILE access beyond
> > 2 Gbytes. 
> > 
> > Lots of applications seem to rely on glibc doing this for them - so it
> > may be you need a newer glibc.
> 
> glibc alone never sets O_LARGEFILE.  It usually needs a recompile
> of the application with -D_FILE_OFFSET_BITS=64 and some testing because
> that may break it. 
> 
> Normally O_LARGEFILE shouldn't be checked on block devices like /dev/sda9 
> though, so it's a bit strange that he gets the error here. 
> 
> strace would probably give clues.

The reason I said glibc was I could not find O_LARGEFILE in the xfs
user space source I looked at, but I could in strace.

Steve

> 
> -Andi
-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


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