All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: NFS List <nfs@lists.sourceforge.net>
Subject: 32 bit stat() on a 64 bit kernel failing on a large NFS filesystem?
Date: Tue, 20 Jun 2006 12:05:20 +0100	[thread overview]
Message-ID: <4497D670.2040900@moving-picture.com> (raw)

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?

Thanks

James Pearson




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

             reply	other threads:[~2006-06-20 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 11:05 James Pearson [this message]
2006-06-20 11:30 ` 32 bit stat() on a 64 bit kernel failing on a large NFS filesystem? Bernd Schubert
2006-06-22 10:44   ` James Pearson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4497D670.2040900@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.