This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:navody:faq:start [03.05.2018 13:26] danecek@cesnet.cz |
en:navody:faq:start [03.05.2018 14:51] danecek@cesnet.cz |
||
---|---|---|---|
Line 311: | Line 311: | ||
=== I want to move my data, but I got problem with permissions. === | === I want to move my data, but I got problem with permissions. === | ||
+ | __Problem description:__ | ||
+ | I tried to transfer my data using Globus/rsync protocol, but I got problem with low permissions, see the log below: | ||
+ | <code>Error (transfer) | ||
+ | Endpoint: ducesnet#globusonline (d8eb370a-6d04-11e5-ba46-22000b92c6ec) | ||
+ | Server: globus.du1.cesnet.cz:2811 | ||
+ | File: /~/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0 | ||
+ | Command: RETR ~/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0 | ||
+ | Message: Fatal FTP response | ||
+ | --- | ||
+ | Details: 500-Command failed. : globus_l_gfs_file_open failed.\r\n500-globus_xio: Unable to open file | ||
+ | /exports/home/username/VO_storage-cache_tape/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0\r\n500- | ||
+ | globus_xio: System error in open: Permission denied\r\n500-globus_xio: A system call failed: Permission denied\r\n500 End.\r\n | ||
+ | </code> | ||
+ | |||
+ | <note important>That issue is typically related to an encrypted files, or files generated by any backup toll.</note> | ||
+ | |||
+ | __Solution:__ | ||
+ | That issue can be solved by checking and setting correct permissions on desired files/directories directly on the data storage. In case you use any system from Windows family, you can use [[en:navody:terminal_windows:start#moba_permissions|this tutorial]]. | ||
+ | |||
+ | Please connect to the data storage using ssh protocol. | ||
+ | |||
+ | <code>ssh username@ssh.du1.cesnet.cz</code> | ||
+ | |||
+ | Now go to the directory, which you wish to check. Here is obvious which files are causing the issue. It is **test1 a testfile1**. | ||
+ | |||
+ | <code>username@store:~>cd VO_storage-cache_tape | ||
+ | username@store:~/VO_storage-cache_tape>ls -alh | ||
+ | total 84K | ||
+ | drwx-----T 4 username storage 82 May 3 09:57 . | ||
+ | drwxr-x--- 1378 root storage 56K May 3 13:30 .. | ||
+ | d--------- 2 username storage 10 May 3 09:56 test1 | ||
+ | drwxr-xr-x 2 username storage 10 May 3 09:56 test2 | ||
+ | ---------- 1 username storage 0 May 3 09:56 testfile1 | ||
+ | -rw-r--r-- 1 username storage 0 May 3 09:56 testfile2 | ||
+ | </code> | ||
+ | |||
+ | If you wish to look for problematic files/directories in the directory tree, you can use following command: | ||
+ | |||
+ | <code># find -L . -perm +u-rwx,g-rwx,o-rwx</code> | ||
+ | |||
+ | Alternatively you can use find command and simultaneously correct missing permissions, see below: | ||
+ | |||
+ | <code># find -L . -perm +u-rwx,g-rwx,o-rwx -exec chmod u+rX '{}' \;</code> | ||