Root: c:\p4\depot\project AltRoots: /mnt/c/p4/depot/project
According to the client definition, if a client is used on Windows, the windows path must be the Root path, and all others must be the AltRoots. So this setup looks correct.
For nearly all operations, this setup works just fine. However, I just tried running fstat on the absolute file path in the bash shell, which generated an error:
$ cd /mnt/c/p4/depot/project $ fstat -Olhp /mnt/c/p4/depot/project/readme.txt Path '/mnt/c/p4/depot/project/readme.txt' is not under client's root 'c:\p4\depot\project'.
Additionally, passing in a relative path generates the same error message. The server version is P4D/NTX64/2018.1/1660568.
This gets even stranger if I add an additional AltRoot path to a path linked to another directory. For example, if the additional AltRoot is '/home/myself/p4/depot/project', then the error reports the client root as '/mnt/c/p4/depot/project'.
Is this a limitation with fstat, or a setup issue, or something else?