This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Call for testing Cygwin snapshot
Charles Wilson <cygwin <at> cwilson.fastmail.fm> writes:
>
> Nope, it was very consistent and did not change over time. One oddity is
> that if you access a file (in a particular view (MVFS-speak for branch,
> more or less)) via the 'multi-view' mount
>
> /cygdrive/m/my_view/my_VOB/some-path-to/some-file
>
> you get (consistently) one number for st_ino and d_ino (call it 'A')
>
> But, if you mount my_view to a drive and access the same file in that
> same view via the mount
>
> /cygdrive/r/my_VOB/some-path-to/some-file
>
> you get (consistently) a different number for st_ino and d_ino (call it
> 'B').
>
> Not sure if that's important (maybe it's expected behavior?)
Expected behavior. According to Corinna's tool:
rootdir: l:\
Volume Name : <CCase>
Serial Number : 36984713
Max Filenamelength : 255
Filesystemname : <MVFS>
Flags:
FILE_CASE_SENSITIVE_SEARCH : TRUE
FILE_CASE_PRESERVED_NAMES : TRUE
FILE_UNICODE_ON_DISK : FALSE
FILE_PERSISTENT_ACLS : FALSE
FILE_FILE_COMPRESSION : FALSE
FILE_VOLUME_QUOTAS : FALSE
FILE_SUPPORTS_SPARSE_FILES : FALSE
FILE_SUPPORTS_REPARSE_POINTS: FALSE
FILE_SUPPORTS_REMOTE_STORAGE: FALSE
FILE_VOLUME_IS_COMPRESSED : FALSE
FILE_SUPPORTS_OBJECT_IDS : FALSE
FILE_SUPPORTS_ENCRYPTION : FALSE
FILE_NAMED_STREAMS : FALSE
FILE_READ_ONLY_VOLUME : FALSE
it seems MVFS does not present useful inode information, so you
are getting the cygwin hash inodes. But the hash is dependent on
the drive letter that the view is mounted under.
--
Eric Blake
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/