Does the user who performs the operation have enough permissions/privileges to do the operation successfully? like restore privilege?
A network trace using /SEC and /B for a similar file for comparison would be useful. Afshin Ross wrote:
Hi guys, I first raised this back in July 2008 on snv_99, but I was very new to Solaris at the time, and don't know if I ever filed a bug. I've just had an email though from somebody asking if I ever found a fix, which has reminded me to have a look at it again. I'm currently running sxce_114. Ordinary use of CIFS is fine, it's joined to our domain, and I have no problem with permissions. However, if I attempt to use robocopy with the /B option to transfer a directory and keep permissions and dates intact, I get the error: "The access control list (ACL) structure is invalid.". The copied files transfer ok, but permission details are lost, the files just inherit the permissions of the folder they are copied to. Strangely, using robocopy with just the /SEC option works fine, and robocopy sets all the permissions correctly. Having done further testing today, I can confirm that this error only happens with robocopy's /B (backup mode) switch. I remember in the past there being talk of known problems with backup programs, was that ever fixed? This is potentially going to be a big problem in our migration from Windows to Solaris CIFS servers as we use date stamps for identifying files to archive, and the /B switch is required if you wish to preserve these. Ross
_______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
