Originally Posted by Valery Reznic
@catkin: "." mean that file has at least one acl set.
@OP: this directory is not NFS-mounted by any chance?
Good to learn about that ".". How does the presence of the . correlate with the gatfacl output in post #4 of this thread which looks the same as getfacl output on a system with no ACLs (I do not have a system with ACLs to test how it would look if ACL(s) were present).
Regards NFS, as long as dhamilton's "No problems reading/writing other files on the volume
" is reliable do we have any reason to suspect that the problem lies at file system level? Whatever the problem is caused by it seems to be specific to this file. Clearly the file can be read or the VM that uses it would not run. That suggests something fine-grained like an ACL or the NTFS permissions that Bull3t wrote about.