We now support mounting and using filesystems with 64-bit inodes even when not mounted with the inode64 option (which now only controls if we allocate new inodes in that space or not). Make sure we a
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 20 Nov 2010 09:29:06 +0100
Could that help with the problem of not being able to mount an NFS share when the top shared dir itself is a 64bit inode? -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Interne
Won't this mean that people exporting non-root directories suddenly have those exports stop working on a kernel upgrade due to changing the handle format? Cheers, Dave. -- Dave Chinner david@xxxxxxxx
Author: Samuel Kvasnica <samuel.kvasnica@xxxxxxxxx>
Date: Mon, 22 Nov 2010 10:05:27 +0100
Hello Dave, nothing is really changing, it is a bugfix. NFS was trying to use 32bit inodes which was incorrect (i.e. broken at client) for xfs filesystem containing 64bit inodes in one special case.
No, if NFSD used ->encode_fh to encode the handle for the export directory we wouldn't even have that problem. NFSD directly encodes i_ino as 32-bit value for the legacy subdirectory export fs handle