As always, thanks for the good info! I put this info in a text file in my general "Useful stuff" directory. If only I had done that last time...
On Wed, 24 May 2000, Guy Harris wrote:
In 5.0, we had to add a file system ID; file handles in 5.0 and later consist of:
32-bit file ID for mount point 32-bit generation count for mount point 8-bit snapshot ID in which file resides 8-bit unused byteThat should have been
32-bit file ID for mount point 32-bit generation count for mount point 16-bit file handle flags 8-bit snapshot ID in which file resides 8-bit unused byte
so the file handle in question becomes (with leading zeroes added, to make it easier to byte-swap them, assuming your NFS clients are big-endian):
02ae0500 mount point file ID (decimal 372226)
51356400 mount point gen count (decimal 6567249)
00 snapshot ID 00 unused 2000 flags (hex 0020, or WAFL_FH_MULTIVOLUME, i.e. it's a 5.0-and-later-format file handle)
000aa5c8 file ID for file (decimal 697800 - remember, this file ID is big-endian, to keep certain NFS clients that use only certain bits of it when hashing their internal per-file-from-NFS-mounted-file-system structures from hashing lots of files to the same bucket)
54417810 gen count for file (decimal 276316500)
5c140000 volume ID for file (decimal 5212, hex 145c)
02ae0500 file ID for export point (decimal 372226) 51356400 snapID/gen for export (decimal 6567249)
----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO