From: Bernd Schubert <bernd-schubert@gmx.de>
Subject: Re: 32 bit stat() on a 64 bit kernel failing on a large NFS
	filesystem?
Date: Tue, 20 Jun 2006 13:30:09 +0200
Message-ID: <200606201330.09563.bernd-schubert@gmx.de>
References: <4497D670.2040900@moving-picture.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
To: nfs@lists.sourceforge.net,
	James Pearson <james-p@moving-picture.com>
In-Reply-To: <4497D670.2040900@moving-picture.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Tuesday 20 June 2006 13:05, James Pearson wrote:
> I recently found a problem running a 32bit (i686) binary on a 64bit
> (x86_64) kernel that fails when stat'ing any file on a multi-TB NFS
> clustered file system (a non-Linux file system).
>
> stat() returns EOVERFLOW (Value too large for defined data type)
>
> The same 32bit binary running on a 32bit kernel stat'ing the same files
> works OK.
>
> In both cases, I'm using RHEL4 based distros on the clients (I also
> tried a generic 2.6.16.x kernel on the 64 bit client, but that made no
> difference).
>
> We can work round the problem by either making sure the binary is
> compiled with _FILE_OFFSET_BITS set to 64, or configuring the NFS file
> server to use 32 bit 'file IDs'.
>
> My question are:
>
> Is this a 'bug' or 'feature' with using a 32 bit app on a 64 bit kernel?
>
> If it's a 'feature', can anyone explain why it works in this way?

I already had the same problem, just see this thread:

http://lkml.org/lkml/2005/2/28/172

-- =

Bernd Schubert
PCI / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs