On Thu, Aug 30, 2012 at 09:44:30AM -0400, Whit Blauvelt wrote: > See: > > http://www.linux-archive.org/centos/639945-xfs-inode64-nfs.html > > Given that my XFS Gluster NFS mount does not have inode64 set (although it's > only 500G, not the 2T barrier beyond which that's evidently strictly > required), and the likelihood that that led to yesterday's problem, what's > the course to fix this? I very much doubt that was the problem. The whole reason that inode64 is not the default is so that inode numbers are kept in the range less than 2^32, precisely so that ancient NFS clients can deal with them.
