An EMC One thread related to a similar topic was found and is stated below.   Apr 23, 2013 10:07 AM (in response to Christopher Imes) Re: are there any Parameters for NFS Exports to Give to the customer? For some of the older versions of AIX that only support 32-bit fileids, the setting on the Isilon NFS export (return-32-bit file ids) needs to be set to support these. An excerpt from Tim Wright's email on this topic below:  Our “inode” values (LIN) are 64-bit. As part of our implementation, and given this huge space, we reserve all of the values that fit into 32 bits for “special” LINs. The upshot is that the LIN or inode number value for every file you will ever see going out over NFS doesn’t fit into 32 bits. This is a problem if you have a OS where the inode type is only 32 bits in size. Most modern Unix-type systems (including Linux) already support 64-bit inode numbers in system calls such as stat(). For those that don’t, if we pass back a 64-bit value, then calls like stat() tend to fail, typically with errno set to ERANGE. By changing the export setting, you cause OneFS to trim off (zero out) the top 32 bits so it doesn’t break these older OSes.
Under Client Compatibility Settings, there is a setting “Return 32 bit File IDs” setting.  Does this mean the export would act like a 32 bit filesystem, with the inodes being able to be seen by 32-bit applications? 
What does the NFS Export setting "Return 32 bit File IDs" mean?