Excellent!!
For months we've had this same problem, but only on a few machines, and
now I expect it was ones with old shortcuts created under 1.5, (and some
machines might also have still had the SMB redirector still installed, to
further confuse things).
Deleting and recreating the shortcuts 'fixed' my test box on which I could
reliably generate this error.
We were initially getting what appeared to be the same error because of
file server > 2TB and the 32-bit device report limits, but the errors
never fully went away after we patched our servers.
Richard
On Aug 23, 2012, at 5:24 PM, Jeffrey Altman wrote:
Shortcuts are tied to the "network provider name" just as drive letter
mappings are.
A shortcut created with the 1.6 or earlier OpenAFS client is using the
Microsoft SMB redirector and the "Microsoft Network" provider.
A shortcut created with the 1.7 or later OpenAFS client is using the
OpenAFS redirector and the "OpenAFS Network" provider.
UNC paths are tied to the network provider. When the "Microsoft
Network" is asked for the path, \\afs\cell\foo it will report that it
doesn't exist even though the file system interface says it does. This
is not a bug but a limitation of the conversion from relying upon
Microsoft's SMB redirector to a dedicated AFS redirector.
Jeffrey Altman
--
Richard Brittain, Research Computing Group,
Computing Services, 37 Dewey Field Road, HB6219
Dartmouth College, Hanover NH 03755
[email protected] 6-2085
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
