Re: question about ntfs_inode_real_open
My question is:
Why assigned the flags of inode by using the file_attributes of STANDARD_INFORMATION? Why not using file_attributes of FILE_NAME_ATTR?
ex. dir0 is a directory, so, I think the value of FILE_NAME_ATTR is right in the below picture.
Why create_time, last_data_change_time, last_mft_change_time and last_access_time are not the same between STANDARD_INFORMATION and FILE_NAME_ATTR?
Well, only Microsoft knows the answer, and ntfs-3g just does the same as Windows....
The picture is actually more complex, as all this is also replicated in each directory in which the file is recorded, and Windows has difficulties maintaining the consistency between the data present in the directories when a file has names in different directories (see remarks in http://msdn.microsoft.com/en-us/library ... 60(v=vs.85
In a directory listing, ntfs-3g displays the information from the file, whereas Windows shows the data from the directory, but if you click on the file, Windows updates the directory information, fixing the discrepancy left by its bad management of multiple names (hard links).