Error accessing mapped drive >2TB?
Fri Oct 23 02:40:00 GMT 2015
On Oct 22, 2015, at 2:34 AM, Corinna Vinschen wrote:
> On Oct 21 11:26, Warren Young wrote:
>> On Oct 21, 2015, at 10:22 AM, Corinna Vinschen wrote:
>>> On Oct 21 09:52, Warren Young wrote:
>>>> I mean, I know how to snag a stream of SMB packets with Wireshark, but
>>>> I don’t know what I’d be looking for in the dump.
>>> Me neither, the Samba guys might be able to help there, perhaps.
>> Apple hasn’t shipped Samba as part of OS X since 10.6, quite a few
>> years ago now. In 10.7, they switched to an internally-developed SMB
> Yes, but the SMB guys can recite the wire format of SMB asleep, probably.
Why would the Samba project’s wizards be motivated to help debug a closed-source piece of software they didn’t write?
If anything, I’d expect them to give Apple the finger for booting Samba out of OS X in the first place.
> There's also
Now we’re talking about *my* motivation, which has only been to test the original report and the fix. I never had this problem — I don’t export whole drives as a matter of principle — and the symptom is now fixed, leaving me without a motivation to learn the SMB protocol.
The only people left with both means and motivation would be at Apple, and then only if they had important software that broke because of their implementation choices. You just fixed the only other known piece of software that breaks.
(Please don’t back out the fix just to put pressure on Apple! :) )
>>> HANDLE handle = CreateFile ("P:\\", ...);
>> I guess I’m not seeing what values to pass to CreateFile()
> Opening a directory requires to use the FILE_FLAG_BACKUP_SEMANTICS flag.
Yes, silly me for not guessing that Windows requires that I tell it I am about to do a backup before I attempt to open a directory for reading. What was so wrong about the design of opendir() that MS had to reinvent it this way?
I also had to fix an error in your original code: GetFileAttributes() takes a path string, not a HANDLE.
After doing both of these things, I now get a new complaint:
Failed to get reparse point: The file or directory is not a reparse point.
I’m reporting this in case it affects the way you want your patch for this problem to react.
Here’s the new program: http://pastebin.com/kUwPrk8v
> Oh and, you have to use the FILE_FLAG_OPEN_REPARSE_POINT flag, of
Adding that doesn’t affect the error I get from the program, so I left it out in the Pastebin version.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin