chmod and chown issues

[tucansam]

I used ssh (root) to move some files, and file permissions ended up messed up, so when I tried to run an rsync backup script, I had issues.

 

'docker safe new permissions' takes hours to run on my array, and I only needed the permissions of one share changed.

 

'chmod 777 *' didn't work.  Failed with an 'invalid option' error.  But 'chmod 777 1*' and then 'chmod 777 2*' and then 'chmod 777 A*' and then 'chmod 777 B*' etc etc etc worked fine.

 

chown, same exact behavior.  'chown -R nobody:users *' failed with an 'invalid option' error.  'chown -R nobody:users A*' B* C* D* etc etc etc worked fine.

 

What did I do wrong?

[remotevisitor]

Do you have a file/directory that starts with a "-", in which case the "*" will be expanding to something that looks like a command option. ?

 

maybe ‘chmod -- 777 *’ might work in that case.

 

[itimpi]

No idea what you did wrong

 

However I wondered if you realised that the New Permissions script can be run against a just a specified share which I would not expect to take that long (rather than the default of all disks/shares)?  You can do it from the GUI or from the command line by using a command of the form
  newperms /mnt/user/sharename