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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=NSCCU5VOqL5gsv4CdIcYfA8J9dCi
	Lm0DCYVto/O3ImVCPqijgVZwd83OzCK7X405yyUsyjlXIFe9bnaLOf3CLhYdqJ/L
	9sO5AAT5n4pjquZ3b8Y/fIfVmhQI/coc+YvNRaLv/dkpkAEOB+UBxJs8tN65SKd0
	t+1GafEHi0NfWII=
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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=t4USWtzF4xsZYXYqkWaE0UVvvxw=; b=rX
	/VHZQjHiulWoMIyCZJqosw9A1M6iHWYZ3hdKkZ07eGG26d3k+K+fmtdYnFj5R/Re
	+nAtw/8nZd80/HpeTOJBAnX6h8O6KfRjvkLahwrTP1vVnsqtiGI0Qy4RhhJKj64/
	ASrY3r53nb7N0KS7oYzpzix6M9iBAovG/KwYdhygE=
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=1.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Error accessing mapped drive >2TB?
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <CA+2x6-L+dr92-O1b2bnqnaCxOzZ9GCLv1ekXEPcALkuYvFp_yQ@mail.gmail.com>
Date: Wed, 16 Sep 2015 18:25:47 -0600
Message-Id: <B35CA86C-3AFD-424A-AFE7-7A2B4FE0B421@etr-usa.com>
References: <CA+2x6-L_pqdN6PHE0c15hcmrmB66Z75Hz95cH+dbcn4yXuVZNg AT mail DOT gmail DOT com> <712A87EA-64C7-4033-BE7F-39C8C8D527EB AT etr-usa DOT com> <110723294 DOT 20150915064630 AT yandex DOT ru> <CA+2x6-LtkKk15AOavG5pUD+YwcKKa=TKU1nnHwEy45LKwLkFJg AT mail DOT gmail DOT com> <0C37A612-5E78-48A8-9503-F3A34129BC7B AT etr-usa DOT com> <CA+2x6-L+dr92-O1b2bnqnaCxOzZ9GCLv1ekXEPcALkuYvFp_yQ AT mail DOT gmail DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8H0Q26M021295

On Sep 16, 2015, at 7:39 AM, Nem W Schlecht <nemws1 AT gmail DOT com> wrote:
> 
> I would think if it was an issue with Mac's SMB implementation, then
> *Windows* would also have some sort of issues with it.  But it shows
> up fine on Windows, I would assume it should show fine in Cygwin as
> well.

More than that: Cygwin doesn’t contain an SMB client.  (I mean, not at the cygwin1.dll level.)  It is just using what Windows gives it.

That’s why I’m grasping at straws like the path error in the strace output, since the only thing that makes sense to me is a problem in the way Cygwin is interpreting what it gets from Windows, rather than the SMB protocol peers doing the wrong thing.

I suppose it could be that Windows Explorer and cygwin1.dll are making different NT kernel syscalls, and that explains the problem.  Lacking a “real” strace on Windows, I’m not sure how to test that.  Maybe Process Monitor could do this?

  https://technet.microsoft.com/en-us/sysinternals/bb896645

There is also this, one of the Google results for “Windows strace”:

  http://www.drmemory.org/strace_for_windows.html
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple