[OpenAFS] Possible bug in Windows AFS client handling older shortcuts

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB866D97A5E4FD0BD5B417A81
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The binary file format is documented here:

http://msdn.microsoft.com/en-us/library/dd871305%28v=3Dprot.13%29.aspx

Section 2.3.2 CommonNetworkRelativeLink


On 8/31/2012 2:52 PM, Dave Botsch wrote:
> I'm wondering if one can somehow "edit" some magic hex value in the .ln=
k
> to update the provider. That way, I could, say, iterate through our afs=

> cell with a script doing the replace on any .LNK files.
>=20
> On Wed, Aug 29, 2012 at 11:39:00AM -0400, Richard Brittain wrote:
>> 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 le=
tter
>>>>>> 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 t=
he
>>>>>> 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
>>
>> --=20
>> Richard Brittain,  Research Computing Group,
>>                    Computing Services, 37 Dewey Field Road, HB6219
>>                    Dartmouth College, Hanover NH 03755
>> Richard.Brittain@dartmouth.edu 6-2085
>> _______________________________________________
>> OpenAFS-info mailing list
>> OpenAFS-info@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-info
>>
>=20


--------------enigB866D97A5E4FD0BD5B417A81
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJQQVvWAAoJENxm1CNJffh4SqsIAMPNvGGXQReDWmfyTrUXbDma
PUSzRFQOctx2A0L/zGh7PgpPl/SsSeDbpXqN6ZslS6TGUC00j9WRvSQx7pfCMX0R
TXDxNQeHlabGfTEPZSzAvftXbeP2NrCn8E5MyUTzMSY9D3VkZPG0TAD1Kv29Jn4z
xUVOfrXBmal7nPsaY0wgLLd07cJd4A3HKbUyMmV+Q0Mr/Z6pVNXROM0sdqH+jIon
E5Kds5y8ZTvorCE2KbzfkyCX0NSJFNG6Bur3/mJlQFMiMF6VWMTzOLx4etqcCDLK
UgWFqUSwaqlVIGCBIrLXFGTUVFWJWrHD+q7V4L5LXtvpf+YFHX8uhuV7Lo1AMf0=
=ftkg
-----END PGP SIGNATURE-----

--------------enigB866D97A5E4FD0BD5B417A81--