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=JnRcWo3ppNoST+uZBPMKaka+BCEY 1I/PEYMF7Mwow2mYUUsI6BVJbv0QsJ/9Z/+aDSbbTUcmN4zKZTu+DGgdfcndqEr5 Gn8Aw2NNnuyqP8I+96yEc3+A+zIEM7QRoQnC6g2MBlUJRwMmGPsgISNZhKGP6he6 ugpQ+chfkWqQhkE= 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=7UVk5LoWUtlKdEbOB8ZuwBwATJ4=; b=GQ /aXFEQEC5uG8d039moSVbZfLCpcoi+Z0qBvbAst3HXtrF0ADvpwdFWZx6SK0w94S NRCcAw36ok7tt4JExf8pThgpo4bgvD/XNqs/NHke7aSzecjvwbdg4AO/IxDY+BHd 9QtjictSJuWiZGrzLB+r+8gwr2blSiUkOiEYi3iTY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=0.9 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 In-Reply-To: Date: Mon, 14 Sep 2015 14:34:12 -0600 Message-Id: <712A87EA-64C7-4033-BE7F-39C8C8D527EB@etr-usa.com> References: To: The Cygwin Mailing List X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8EKYVCe021558 On Sep 12, 2015, at 11:14 AM, Nem W Schlecht wrote: > > The only thing I can think of is that the 2nd drive is >2TB. The same thing happens here with a 3.1 TB Fusion drive and a 500 GB external drive, so no, I don’t think the volume size is the real issue. I assume you are seeing the same thing that I am, that Explorer shows the root contents of both drives just fine? When I strace’d an ls of one of these root shares here, I got 764 lines of…emissions, of which this section seems the most interesting to me: 1051 263166 [main] ls 4720 stat64: entering 625 263791 [main] ls 4720 normalize_posix_path: src /p 609 264400 [main] ls 4720 normalize_posix_path: /p = normalize_posix_path (/p) 630 265030 [main] ls 4720 mount_info::conv_to_win32_path: conv_to_win32_path (/p) 653 265683 [main] ls 4720 mount_info::cygdrive_win32_path: src '/p', dst 'P:\' 668 266351 [main] ls 4720 set_flags: flags: binary (0x2) 674 267025 [main] ls 4720 mount_info::conv_to_win32_path: src_path /p, dst P:\, flags 0x4022, rc 0 1168 268193 [main] ls 4720 symlink_info::check: 0x0 = NtCreateFile (\??\P:\) 10641 278834 [main] ls 4720 symlink_info::check_reparse_point: NtFsControlFile(FSCTL_GET_REPARSE_POINT) failed, 0xC0000275 839 279673 [main] ls 4720 symlink_info::check: not a symlink 1049 280722 [main] ls 4720 symlink_info::check: 0 = symlink.check(P:\, 0x24B620) (0x4022) 655 281377 [main] ls 4720 path_conv::check: this->path(P:\), has_acls(0) 640 282017 [main] ls 4720 stat_worker: got 5 error from path_conv 757 282774 [main] ls 4720 __set_errno: int stat_worker(path_conv&, stat*):1933 setting errno 5 714 283488 [main] ls 4720 stat_worker: -1 = (\??\P:\,0x600042080) Why errno 5 from path_conv? Yes, I am one of those evil people who edit cygdrive out of /etc/fstab so I can use /x, where x=drive letter. :) -- 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