So it looks like CYGWIN is deciding to invoke some oddball i-node fabrication when a file is located on a CIFS share and actually use the NTFS value when it's NTFS. Maybe the logic is designed to support the FAT32 scenario and they never accounted for CIFS.
The 'IndexNumber: 0x81f' valued returned by Samba is the actual i-node value. I might post a report to CYGWIN on this and see what they say. Thanks for the help! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
