Skip to content

mv command ‐ ACL issue

Martin Ayling edited this page Sep 13, 2024 · 1 revision

The mv command on the HPC will move the data and the associated permissions (ACL), so the moved data can only be accessed by Users who are members of that source ACL. This should not affect access when moving data within an EI Project, but may impact access when moving data between EI Projects.

Moving forward, when using Linux on the HPC, the cp (or cp -R) command can be used so that the data copied in the destination location inherits the ACL from the destination, and then the original source data can be (carefully) removed (rm or rm -R) if required. Ideally, it is suggested that you source rsync to copy data; this will maintain timestamps for data as well as inheriting the permissions of the new location. Note that rsync does not (as of 12/9/24) appear to maintain owner/group information for files transferred like this.

Alternatively, if you have access permissions, data can be dragged across from one EI Project to another EI project using a mapped/mounted (SMB) drive and the data copied in the destination location inherits the ACL from the destination. This transfer method should work for transferring data in chunks up to around 500GB, but larger data transfers may be slow depending on the machine being used, network connectivity, etc.

Clone this wiki locally