On 9/24/2014 2:35 PM, Dave Botsch wrote: > Hi. > > What's the story with case insensitivity or sensitivity with the Windows > OAFS client?
File and directory name searches are performed:
1. case sensitive first
2. case insensitive second
Ambiguous case insensitive matches are failed.
> Of course, OpenAFS is case sensitive and Windows is not. So, does the
> client attempt to resolve things irrespective or case or should it fail
> if indeed the case doesn't match?
>
> In this specific case, Corel Draw is attempting a CreateFile call on a
> path into AFS with everything completely capitalized (why Corel Draw
> does this in some cases and in others has the path correctly upper and
> lowered, dunno). When Corel does the all caps, according to Process
> Monitor, the operation fails with PATH_NOT_FOUND.
>
> Looking at DebugView with fs trace on ... I see:
>
> cm_EvaluteVolumeReference for string
> [@vol:CNF.CORNELL.EDU#HOME.STAFF.DWB7]
> Found cell [CNF.CORNELL.EDU] and volume [HOME.STAFF.DWB7]
> RDR_EvaluateNodeByName FAILURE code=0x6654321d status=0xc000003a
>
> I see that 0xc000003a is indeed STATUS_OBJECT_NOT_FOUND
>
> So, this makes me wonder why if I in the start menu were to type in the
> same full path in all caps, a windows explorer window opens with the
> folder.
>
> Should this be reported as an OpenAFS bug or do I need to engage Corel
> to try and get them to use case sensitive paths in their calls?
The fact that Corel is issuing the request in all upper case is most
likely a bug either in Corel, or in a file system filter driver, or in
OpenAFS. Many application and filter driver vendors hard code the file
system type into their products. They assume that if the file system
does not advertise itself as NTFS or CIFS that it is FAT. As a result
they issue the request in all upper case.
However, this application or file system filter behavior might also be
triggered by a run time test that returns an unexpected behavior. That
behavior might be a bug in OpenAFS or it might not be. It might be the
lack of a feature that Corel relies upon such as Extended Attributes or
Alternate Data Streams or DOS File Attributes or anything else.
If you have free support with Corel, then file the bug with them. If
not, decide who you want to pay:
1. Corel since it is their application that is visibly experiencing
the problem
2. Microsoft because it is their operating system and Corel might
require that Microsoft debug the kernel first.
3. An OpenAFS support provider. I suggest you hire one of the entities
that wrote the code.
Tracking down the root cause of issues like this typically takes days of
effort.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
