DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=XAqHXENwyg3yG8cq
	gu4xZbB6d5buHpRalFN9t4f5QWLYqNHkoT3ivddSYo+pdbwMtKZhv4mtJoZf6nxT
	/vBkbb9xUA+TRii797cEHYCd6j8ny8siDL+JWjRINpV2kSE5qE3hLguGjqywfqr7
	m0/a4QqX+9DGqUITnxPj9qVtTEw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 24 Oct 2015 03:37:04 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <836425854.20151024033704@yandex.ru>
To: Warren Young <wyml@etr-usa.com>, cygwin@cygwin.com
Subject: Re: Error accessing mapped drive >2TB?
In-Reply-To: <30B1BBD5-E147-4020-B31D-37475AEE9B7B@etr-usa.com>
References: <CA+2x6-L_pqdN6PHE0c15hcmrmB66Z75Hz95cH+dbcn4yXuVZNg@mail.gmail.com>   <712A87EA-64C7-4033-BE7F-39C8C8D527EB@etr-usa.com>  <20151021100328.GL5319@calimero.vinschen.de>  <CB8461F5-FB0E-44D8-81BB-B52DD02AD400@etr-usa.com>  <20151021162254.GC19868@calimero.vinschen.de>  <169BF9F6-FF26-4073-9CC4-786882EFBAE9@etr-usa.com>  <20151022083446.GW5319@calimero.vinschen.de>  <B8DBF0B5-51A9-4833-92D5-CA9E08B27DEC@etr-usa.com>  <20151023092007.GF5319@calimero.vinschen.de>  <562A4495.5010705@secure-endpoints.com>  <30B1BBD5-E147-4020-B31D-37475AEE9B7B@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Greetings, Warren Young!

>> Apple should have registered with Microsoft their own reparse point tag.
>> Instead they broke the rules and used Microsoft's
>> IO_REPARSE_TAG_MOUNT_POINT

> If Apple uses their own tags, wouldn’t that cause the Windows SMB client to
> be unable to understand Unix mount points, when if it comes across them?

My understanding is that the data stored in reparse point is not intended for
end user (in this case, client system's Explorer) consumption, but solely
exists for the benefits of the host file system management driver.

> I don’t see that the Apple SMB server really needs to report Unix mount
> points at the root of a share, but they could also appear in the middle of a
> share, at which point I assume there are important implications to SMB,
> equivalent to the inode uniqueness problem on Unix.

> Therefore, I can see that Apple’s SMB server needs a way to tell the client
> that it is crossing a filesystem boundary.
> The question is, is the way Apple chose  a sensible one?

The very presence of the reparse point attribute is all that client system
needs to know. The data stored in it is (supposedly) of little utility outside
the host filesystem.


-- 
With best regards,
Andrey Repin
Saturday, October 24, 2015 03:32:00

Sorry for my terrible english...