Hello, Ran into a quirk that caused some trouble.
For some reason CYGWIN 1.7.5 (I know this is old) is constructing inode values for files on Samba (3.6.4) shares with a different algorithm than is used for files on NTFS volumes. This caused a script that checks for matching hard-links to fail. Confirmed that Samba is returning the actual inode values in 'IndexNumber' with 'procmon' while running the stat -c '%h %d %i' filename command. See https://lists.samba.org/archive/samba/2012-May/167381.html. Is CYGWIN mistaking the Samba share for a FAT32 volume and using an inode-faking algo? Or is it something else? Was this fixed in a newer version of CYGWIN? I did try a search but came up with nothing. With NTFS the inode values reported do match the underlying 'IndexNumber' value. Please CC me with any replies as I am not subscribed to the list. Thanks -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
