Isilon uses 64 bit by default.  Any NFS export that should use 32 bit would need to be specified to only use 32 bit.    You could setup a 32 bit Export and another with the default of 64 bit.    It's no longer a sysclt (sysctl vfs.nfsrv.do_32bit_fileid=1) setting in 6.5.X. You have use the isi nfs cmd and it's should be persistent on reboots unlike before you have to put it in the mcp override sysclt.conf file.  If you want to set the options for all exports, use the '-s' flag as follows. For a specific export, replace '-s' with '-i'. You can find the rule ID for a given export with 'isi nfs exports list'  # isi nfs exports modify -s --return-32bit-file-ids=yes    Hope this helps,
We have a site with some 32-bit Linux server running applications.  When they running applications will show error.  After we use 32-bit file IDs over NFSv3, those applications can run smoothly.  My question is…  What should we pay more attention when we use 32-bit file IDs over NFS?  Does it will limit all 64-bit file IDs environment? Connections or file size will be impact too?
32-bit Linux applications on Isilon question