Error accessing mapped drive >2TB?
Corinna Vinschen
corinna-cygwin@cygwin.com
Wed Oct 21 12:43:00 GMT 2015
On Oct 21 15:33, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
Your mailer is breaking the history, btw. Could you reconfigure so the
"blah wrote:" header is preserved for each mail in the thread you still
quote? Thanks.
> > Probably because of the above
>
> > symlink_info::check_reparse_point: NtFsControlFile(FSCTL_GET_REPARSE_POINT)
> > failed, 0xC0000275
>
> > This is in fact a weird error code in this scenario.
>
> > Consider that symlink_info::check_reparse_point is *only* called, if the
> > file to check (here "P:\") has the FILE_ATTRIBUTE_REPARSE_POINT flag
> > set. So from the Windows perspective it is certainly a reparse point.
>
> > Cygwin checks the flag to allow evaluating of reparse points as symlinks.
> > If the flag is set, it calls symlink_info::check_reparse_point which in
> > turn calls
>
> > status = NtFsControlFile (..., FSCTL_GET_REPARSE_POINT, ...);
>
> > to fetch the target information the reparse point points to, in POSIX
> > terms the symlink target. But *this* call returns a status of 0xC0000275,
> > which means STATUS_NOT_A_REPARSE_POINT. And since it's totally unexpected
> > that NtFsControlFile fails on a reparse point, the code sets errno to EIO.
>
> > Hang on.
>
> > 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?
>
> That's… interesting.
> Windows does not allow for reparse points to networked locations.
> Symlinks all right, directory junctions no.
Fine, but then the question is, why is the FILE_ATTRIBUTE_REPARSE_POINT
flag set in the first place?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20151021/3ca6bd3c/attachment.sig>
More information about the Cygwin
mailing list