On 11/10/2015 11:46 AM, Jan Pospíšil wrote: > Hello, I am using git with repositories on AFS and I am getting the > following errors > > error: unable to open object pack directory: ./objects/pack: Function > not implemented > > when working with the repository on a Windows machine (win10 64bit, > openafs-client 1.7.3100, git 2.6.2.windows.1).
Please try the 1.7.3301 installation package from https://www.auristor.com/openafs/client-installer and see if you can still reproduce the problem. However, I doubt it will make a difference (see below): > The issue is fully > described here: > > https://github.com/git-for-windows/git/issues/510 I would also suggest that instead of using drive letter mappings that you might try the flat unc paths //afs/..... > One git guy said that it is a problem with OpenAFS on windows and not > git. I have to admit that if I work with the repository on AFS > filesystem in other OSes (Linux Debian, Mac OSX, ...) they are fully > operational without any error, so my impression is that the error might > be either in git for windows or in openafs-client for windows, or both. > Unfortunately I do not know how to debug the problem any further. They say that the problem is not with the msys/cygwin layer but that Win32 functions they are calling directly are returning a function not supported error. That could very well be. They do not say what the unsupported function might be. However, there is a large amount of file system functionality that WinAFS simply cannot support because there is no equivalent functionality in the AFS3 protocol: * extended attributes * alt data streams * windows security (acls) * certain dos attributes * cross directory hard links * oplocks There are a variety of sub functions that cannot be implemented. You do not say in your report whether this problem is new to the msysGit 2.x series or were you also experiencing it with the msysGit 1.x series which relied more heavily on the msys/cygwin posix environment instead of native Win32 file system calls. > > Is there someone in the list who could for example try to reproduce the > error? I will look at some point but I cannot promise when I would get around to investigating this issue. If this is time critical you might want to consider a paid support request. https://www.auristor.com/openafs/technical-support/request-support > Could someone tell me how one could debug the problem in order to detect > the core of the problem? In the release notes that are installed on disk (chm file) there is an appendix with troubleshooting tips. The first place to start is using SysInternals Process Monitor to trace the activity from the git processes to \\afs\.... and see which operations (if any) fail. > > Thank you very much in advance. > > Kind regards > Jan Pospisil Jeffrey Altman Founder and CEO AuriStor, Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
