[OpenAFS] OAFS 1.7.x Win and Case (In)Sensitivity

Dave Botsch botsch@cnf.cornell.edu
Wed, 24 Sep 2014 14:35:21 -0400


What's the story with case insentitivy or sensitivity with the Windows
OAFS client?

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
  Found cell [CNF.CORNELL.EDU] and volume [HOME.STAFF.DWB7]
RDR_EvaluateNodeByName FAILURE code=0x6654321d status=0xc000003a

I see that 0xc000003a is ineed 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

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?


David William Botsch