cc_staff
633
edits
Transferring data: Difference between revisions
Jump to navigation
Jump to search
suggest "rsync -rltv"
No edit summary |
(suggest "rsync -rltv") |
||
| Line 54: | Line 54: | ||
<!--T:26--> | <!--T:26--> | ||
Some users have encountered trouble when using <code>rsync</code> to transfer directories into <code>/project</code>. The <code>-p</code> and <code>-g</code> flags (or equivalently <code>--perms</code> and <code>--group</code>) may cause the group ownership of files to be incorrectly set. Since quotas in <code>/project</code> are enforced based on group ownership this in turn may lead to <code>Disk quota exceeded</code>. The frequently-used <code>-a</code> or <code>--archive</code> flag implies <code>-p</code> and <code>-g</code>. Best advice is to use Globus instead of rsync, but if you choose to use rsync, do not use <code>-p</code> and <code>-g</code>. | Some users have encountered trouble when using <code>rsync</code> to transfer directories into <code>/project</code>. The <code>-p</code> and <code>-g</code> flags (or equivalently <code>--perms</code> and <code>--group</code>) may cause the group ownership of files to be incorrectly set. Since quotas in <code>/project</code> are enforced based on group ownership this in turn may lead to <code>Disk quota exceeded</code>. The frequently-used <code>-a</code> or <code>--archive</code> flag implies <code>-p</code> and <code>-g</code>. Best advice is to use Globus instead of rsync, but if you choose to use rsync, do not use <code>-p</code> and <code>-g</code>. | ||
Therefore '''<code>rsync -rltv ...</code>''' is a good replacement for <code>rsync -av ...</code> when syncing files into the <code>/project</code> filesystem. | |||
===Using checksums to check if files match=== <!--T:13--> | ===Using checksums to check if files match=== <!--T:13--> | ||