So the directory we are copying to does not have smartlock enabled on it.

i am at a loss at this point.

upon further examination, it seems like the folder get created however nothing copies after that.

it seems the errors step when the account tries to modify attributes on folders after copying to the isilon

i am already a backup operator and administrator on the isilon.

Thanks Ned,

this is the output of the folder where i copy data to.

Below the data folder, if i migrate a MARKETING folder with sub folder and files, all the sub folders are created but then it never copies files because the software tries to change some metadata on the folders and has access denied.

Its something with the isilon as i have tried this on vnx, netapp and windows and it works fine.

something on the isilon is preventing from changing some attributes to the folders such as permissions for creator owner possibly and it fails out.

i do appreciate your time.

and as for permissions, i have made the account that is making the changes to run as root and also tried full permissions for the share and nothing works.

its also part of the local admins and backup operators.

what tool are you using to copy the data ? If it's emcopy/robocopy tell it to omit copying the ACLs ..see if that works.  I had a similar issue where the directories would get created on Isilon ( i was copying form Celerra NS80) but nothing inside of them would copy and the modified date would change to 1980. I ended up setting ACLs on target (luckily it was very flat ACL structure) and told robocopy to skip ACLs, just copy the data.

try command  below

chmod -bR 777

Chris,

if you look at the first paragraph of OP , he is running "as root"

Gentlemen,

This is not at all an issue with Filesystem permissions.  What you're seeing here instead is the fact that even with:

• Share Full Control
• Member of Local Administrators on Isilon
• Member of Backup Operators on Isilon

That your copy tool is unable to set ownership during it's copy and is most likely abandoning its copy pass as a result.  This is because when migrating data to Isilon in this manner, you must give the account doing the copy (and only that account), run-as-root permissions at the share level.  Be 100% certain that after cutover you remove this, but for ingesting data and retaining permissions it is a must.

I hope this helps,

Chris Klosterman

Senior Solution Architect

EMC Isilon Offer & Enablement Team

chris.klosterman@emc.com

twitter: @croaking

kevangelakos wrote: i create a user mapping to give the sid from the ad account to the root account and after that mapping was done everything was applied without any errors.

how did you do it ?