I can reproduce the behavior you demonstrate.
Would this problem have the effect of preventing the proper ACLs to be set on
copied directories, and then preventing any files from being copied to those
directories? That's what I am seeing... The full directory structure is
created, but the ACLs are not set properly on the directories, and no files
are copied. The unresolvable SIDs are not added, and also the built-in SIDs
are not duplicated. If the unresolvable SIDs are removed from all of the source
files and directories, then the robocopy works without any problems.
Thank you.
On Fri, 3 Oct 2008 17:33, Nicolas Williams wrote:
> On Fri, Oct 03, 2008 at 05:25:51PM -0500, Nicolas Williams wrote:
>>> I'm investigating a possible bug in unresolvable SID ID mapping.
>
> You can observe the bug I'm investigating like so:
>
> % idmap show -c sid:S-1-5-1-2-3-4-1
> sid:S-1-5-1-2-3-4-1 -> uid:2162761759
> % idmap show -c sid:S-1-5-1-2-3-4-1
> sid:S-1-5-1-2-3-4-1 -> uid:2162761760
> % idmap show -c sid:S-1-5-1-2-3-4-1
> sid:S-1-5-1-2-3-4-1 -> uid:2162761761
> %
>
> Whereas:
>
> % idmap show -c usid:S-1-5-1-2-3-4-2
> usid:S-1-5-1-2-3-4-2 -> uid:2162761764
> % idmap show -c usid:S-1-5-1-2-3-4-2
> usid:S-1-5-1-2-3-4-2 -> uid:2162761764
> % idmap show -c usid:S-1-5-1-2-3-4-2
> usid:S-1-5-1-2-3-4-2 -> uid:2162761764
> %
>
> Basically, if the caller doesn't know the type of a given unresolvable
> SID (and why should they?) then you get a different UID/GID every time.
> Actually, that happens even if you claim it's a group ('gsid').
>
> When that happens only the last UID/GID returned then resolves back to
> the original SID.
>
> Nico
> --
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
