X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=BpOTtRrdURS9k/cZYtjCEaVXDgzJunWbQIOkWlqwIvhxGbw54wuXO
	NxXoawbdDgIc8XCcts1FNWy9LQyH7W1bHoneVpGDtSuiHA4C+cXgg4hgGcv7NaHJ
	+GkllBDEVy1ZX6XyXB5dijaob4bTlyi8NHylkl5O5wC2NjPcfToFpg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=z+ep+e9WhNO9m6sjpcRng6zCEig=; b=S4agWlcSb2bZXxcV3QimCqhS4tCH
	eppSp/wgT/dwtTUNB9x38q0nlzotgl9ZBgeAH1Mt6a3o+Ii2uqBj8oRXQoajkXl0
	ad5hC7cyH3tSbdLGVI9lUS8Ok5FHoxisSFpCImsFP/xr/2R2jdfFmKjustSl8hW3
	ATK9r1A+wAFLV3Y=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Wed, 21 Oct 2015 18:22:54 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Error accessing mapped drive >2TB?
Message-ID: <20151021162254.GC19868@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CA+2x6-L_pqdN6PHE0c15hcmrmB66Z75Hz95cH+dbcn4yXuVZNg AT mail DOT gmail DOT com> <712A87EA-64C7-4033-BE7F-39C8C8D527EB AT etr-usa DOT com> <20151021100328 DOT GL5319 AT calimero DOT vinschen DOT de> <CB8461F5-FB0E-44D8-81BB-B52DD02AD400 AT etr-usa DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="3siQDZowHQqNOShm"
Content-Disposition: inline
In-Reply-To: <CB8461F5-FB0E-44D8-81BB-B52DD02AD400@etr-usa.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--3siQDZowHQqNOShm
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Oct 21 09:52, Warren Young wrote:
> On Oct 21, 2015, at 4:03 AM, Corinna Vinschen wrote:
> >=20
> > The FILE_ATTRIBUTE_REPARSE_POINT flag is set but when calling a function
> > to fetch the reparse data it's no reparse point anymore?  How dumb is
> > that?
> >=20
> > I can't reproduce this bug with my Samba drives, but it's not actually a
> > bug in Cygwin from my perspective.
> >=20
> > Yeah, that observation doesn't really help, so I applied a potential
> > workaround to Cygwin.
>=20
> How could we prove that the problem is the Apple SMB server?
>=20
> I mean, I know how to snag a stream of SMB packets with Wireshark, but
> I don=E2=80=99t know what I=E2=80=99d be looking for in the dump.

Me neither, the Samba guys might be able to help there, perhaps.
Or, does wireshark know how SMB packages look like OTW?

Alternatively, a native Windows test application like this should
show the same symptom:

  HANDLE handle =3D CreateFile ("P:\\", ...);
  DWORD attributes =3D GetFileAttributes (handle);
  if (attributes !=3D (DWORD) -1
      && (attributes & FILE_ATTRIBUTE_REPARSE_POINT))
    {
      char buf[32000];
      DWORD len;

      if (!DeviceIoControl(handle, FSCTL_GET_REPARSE_POINT, NULL, 0,
			   buf, 32000, &len, NULL))
        printf ("error %u\n", GetLastError ());
    }

If so, the error code would be 4390.

> Keep in mind that Windows Explorer seems to cope with this situation,
> so Explorer may be doing something like in your patch.

Yeah, maybe.  Or it doesn't even test for a reparse point in this
scenario.

> > If you're set up to build your own Cygwin, please give it a try.
>=20
> Yes, that fixes the symptom here.
>=20
> Thanks for chasing this down.

Thanks for testing!


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--3siQDZowHQqNOShm
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWJ7veAAoJEPU2Bp2uRE+gv9MP/jb0T74PgvTz6SBun1l5OCZJ
/DjB10Ubl16bqDPemu+UiT701Qgkfa0UZ3BYxlwf9uVJV69Q1uHTyG0VEMYb9PeT
7+nxJreBxsd96IyJRdXCOVmee391g8pYlpXze5hOwXT6rKYTiNMzPrLgcQyqsFUp
H9yb6cgX+OWMj3ZT7hH/0GYia6RCNnZuUuTP4F9kt4L/W0PiOlSvJTdppHx139cU
YJ0yJ0IiWnjN4ztMGXhG6CN1ToiZfts1r88WNqlg150p5vjIObCL9vzOtt4EstzD
asrFSw+J5Grn1YHjXjnfXtcVM7GX4z85HBqC4RwhNI3iZLZp8/hA8s366E3l2ona
2L76zhGm63LMBqC71FvIaL42kn5knVlYpdqCSQVgWDvxFUJ2izmrOidq4C1c4qF+
2U27PJPtm7eRT3OKfJ7LwvH4yTsr0AKdnYcKG8R5wQrNK5AB6TJi6DxritkMh9II
u/uYuSnvgflaTEbki3vusVR13A4yj7JdFHQmNNo0yt//kwr+gbUq4pNREua44HdU
K0C8JKOHqylNxpttexj16FKW1ntvsqeK5u5/DSELndZhwbsRRL6SzqlxKQ6tvfYV
nwfg28+jxV25wvVxhGferPGilYE/B4/TEKLyzp8vIneHfyNDbzkaS6rAFI9qM7N4
EJuU7Q3pbnpBiyW08jvI
=ba+E
-----END PGP SIGNATURE-----

--3siQDZowHQqNOShm--