| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: Anyone know what this error means? |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Wed, 9 Jan 2002 19:05:17 +0100 |
| Cc: | Adam McKenna <adam-dated-1010968404.3db79f@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1010588784.29727.30.camel@xxxxxxxxxxxxxxxxxxxx> |
| References: | <20020109003323.GW4511@xxxxxxxxxxxx> <1010588784.29727.30.camel@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.22.1i |
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. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Anyone know what this error means?, Derek Glidden |
|---|---|
| Next by Date: | Re: Anyone know what this error means?, Andi Kleen |
| Previous by Thread: | Re: Anyone know what this error means?, Steve Lord |
| Next by Thread: | Re: Anyone know what this error means?, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |