This is the mail archive of the
mailing list for the Cygwin project.
Re: Error accessing mapped drive >2TB?
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Wed, 16 Sep 2015 18:25:47 -0600
- Subject: Re: Error accessing mapped drive >2TB?
- Authentication-results: sourceware.org; auth=none
- 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>
On Sep 16, 2015, at 7:39 AM, Nem W Schlecht <email@example.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
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?
There is also this, one of the Google results for âWindows straceâ:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple