On 04.10.2021 21:25, Mark Harmstone wrote: > Kari, Konstantin, what's your conclusion on this? Do you agree that > case-insensitivity is broken at present, or is there something screwy > going on with my set-up? > > Mark Hello. Right now we can create two files "File" and "file" on ntfs3. If we won't force case sensitivity, then it will become one and same file. The same behavior you can see in CreateFileA function with FILE_FLAG_POSIX_SEMANTICS [1] or in NtSetInformationFile function with FileCaseSensitiveInformation [2]. So it's expected for `ls WINDOWS` to fail. Should ntfs3 be the exact copy of windows api or not? (ntfs.sys is case sensitive). Should ntfs3 work with `ls WINDOWS`? As I see, Microsoft makes steps towards case sensitivity. There is indeed some dubious code with ntfs_cmp_names_cpu / ntfs_cmp_names. We must always compare filenames with bothcase == true. There will be patch to fix this situation. Thanks for telling about this problem. [1]: https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea [2]: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-ntifs-ntsetinformationfile
