http://techwiki.co.uk/index.php?action=history&feed=atom&title=RClone_-_Local_FileSystemRClone - Local FileSystem - Revision history2026-05-17T15:03:55ZRevision history for this page on the wikiMediaWiki 1.34.0http://techwiki.co.uk/index.php?title=RClone_-_Local_FileSystem&diff=133&oldid=prevAdam.birds: Created page with "=Local FileSystem= =Usage= Local paths are specified as normal filesystem paths, eg '''/path/to/wherever''', so <pre> rclone sync /home/source /tmp/destination </pre> Will..."2016-04-30T15:55:07Z<p>Created page with "=Local FileSystem= =Usage= Local paths are specified as normal filesystem paths, eg '''/path/to/wherever''', so <pre> rclone sync /home/source /tmp/destination </pre> Will..."</p>
<p><b>New page</b></p><div>=Local FileSystem=<br />
<br />
=Usage=<br />
<br />
Local paths are specified as normal filesystem paths, eg '''/path/to/wherever''', so<br />
<br />
<pre><br />
rclone sync /home/source /tmp/destination<br />
</pre><br />
<br />
Will sync '''/home/source''' to '''/tmp/destination'''<br />
<br />
These can be configured into the config file for consistencies sake, but it is probably easier not to.<br />
<br />
=Modified Time=<br />
<br />
Rclone reads and writes the modified time using an accuracy determined by the OS. Typically this is 1ns on Linux, 10 ns on Windows and 1 Second on OS X.<br />
<br />
=Filenames=<br />
<br />
Filenames are expected to be encoded in UTF-8 on disk. This is the normal case for Windows and OS X.<br />
<br />
There is a bit more uncertainty in the Linux world, but new distributions will have UTF-8 encoded files names. If you are using an old Linux filesystem with non UTF-8 file names (eg latin1) then you can use the '''convmv''' tool to convert the filesystem to UTF-8. This tool is available in most distributions’ package managers.<br />
<br />
If an invalid (non-UTF8) filename is read, the invalid caracters will be replaced with the unicode replacement character, ‘�’. '''rclone''' will emit a debug message in this case (use '''-v''' to see), eg<br />
<br />
<pre><br />
Local file system at .: Replacing invalid UTF-8 characters in "gro\xdf"<br />
</pre><br />
<br />
==Long Paths on Windows==<br />
<br />
Rclone handles long paths automatically, by converting all paths to long <span class="plainlinks">[https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath UNC paths]</span> which allows paths up to 32,767 characters.<br />
<br />
This is why you will see that your paths, for instance '''c:\files''' is converted to the UNC path '''\\?\c:\files''' in the output, and '''\\server\share''' is converted to '''\\?\UNC\server\share'''.<br />
<br />
However, in rare cases this may cause problems with buggy file system drivers like <span class="plainlinks">[https://github.com/ncw/rclone/issues/261 EncFS]</span>. To disable UNC conversion globally, add this to your '''.rclone.conf''' file:<br />
<br />
<pre><br />
[local]<br />
nounc = true<br />
</pre><br />
<br />
If you want to selectively disable UNC, you can add it to a separate entry like this:<br />
<br />
<pre><br />
[nounc]<br />
type = local<br />
nounc = true<br />
</pre><br />
<br />
And use rclone like this:<br />
<br />
<pre><br />
rclone copy c:\src nounc:z:\dst<br />
</pre><br />
<br />
This will use UNC paths on '''c:\src''' but not on '''z:\dst'''. Of course this will cause problems if the absolute path length of a file exceeds 258 characters on z, so only use this option if you have to.<br />
<br />
[[Category:RClone]]<br />
[[Category:Linux]]<br />
[[Category:Contents]]</div>Adam.birds