Harry
June 14, 2020, 3:57pm
1
Command :
rclone copy testfile.zip gdrive1: -vv
Output :
2020/06/14 21:24:02 DEBUG : rclone: Version "v1.52.1" starting with parameters ["rclone" "copy" "testfile.zip" "gdrive1:" "-vv"]
2020/06/14 21:24:02 DEBUG : Using config file from "C:\\Users\\HARRY\\.config\\rclone\\rclone.conf"
2020/06/14 21:24:02 DEBUG : fs cache: renaming cache item "testfile.zip" to be canonical "//?/C:/Users/HARRY"
2020/06/14 21:24:02 DEBUG : testfile.zip: Need to transfer - File not found at Destination
2020/06/14 21:24:06 DEBUG : testfile.zip: MD5 = 4366745d03859d29f5abb7b36f754c82 OK
2020/06/14 21:24:06 INFO : testfile.zip: Copied (new)
2020/06/14 21:24:06 DEBUG : 4 go routines active
I am not using any cache, then why does it show fs cache: renaming cache item
?
It just needs to have the path to the item to get it, it's not really 'caching' anything.
felix@gemini:/etc$ rclone copy hosts GD: -vv
2020/06/14 12:04:38 DEBUG : rclone: Version "v1.52.1" starting with parameters ["rclone" "copy" "hosts" "GD:" "-vv"]
2020/06/14 12:04:38 DEBUG : Using config file from "/opt/rclone/rclone.conf"
2020/06/14 12:04:38 DEBUG : fs cache: renaming cache item "hosts" to be canonical "/etc"
2020/06/14 12:04:38 DEBUG : hosts: Size and modification time the same (differ by -273.054µs, within tolerance 1ms)
2020/06/14 12:04:38 DEBUG : hosts: Unchanged skipping
2020/06/14 12:04:38 INFO :
Transferred: 0 / 0 Bytes, -, 0 Bytes/s, ETA -
Checks: 1 / 1, 100%
Elapsed time: 0.0s
2020/06/14 12:04:38 DEBUG : 4 go routines active
That's normal stuff.
Harry
June 14, 2020, 4:06pm
3
Hmm. But this wasn't the case before.
asdffdsa
(jojothehumanmonkey)
June 14, 2020, 4:07pm
4
rclone has to convert file paths and remote paths into its own format.
every time you run rclone, you will see that.
for example, on windows computers.
fs cache: renaming cache item "C:\\Users\\user01\\AppData\\Local\\Temp\\kdbx\\zip\\kdbx.20200613.123033.7z" to be canonical "//?/C:/Users/user01/AppData/Local/Temp/kdbx/zip"
1 Like
asdffdsa
(jojothehumanmonkey)
June 14, 2020, 4:09pm
5
yes, that is correct,
at some point rclone started to put that into the debug log.
i just checked some of my log file and i think this started with v1.52.0
1 Like
I think it's from 1.51 as this is from the changelog:
When renaming files in the cache, rename the cache item in memory too (Nick Craig-Wood
The debug line is here:
return f, ok, err
})
if err != nil && err != fs.ErrorIsFile {
return nil, err
}
f = value.(fs.Fs)
// Check we stored the Fs at the canonical name
if created {
canonicalName := fs.ConfigString(f)
if canonicalName != fsString {
fs.Debugf(nil, "fs cache: renaming cache item %q to be canonical %q", fsString, canonicalName)
value, found := c.Rename(fsString, canonicalName)
if found {
f = value.(fs.Fs)
}
addMapping(fsString, canonicalName)
}
}
return f, err
}
asdffdsa
(jojothehumanmonkey)
June 14, 2020, 9:11pm
7
well, i did check my logs. none from 1.51.0 has that fs cache entry
here are two logs, run one day apart.
first log snippet is 1.51.0
second log snippet is 1.52.0
2020/06/07 14:40:34 DEBUG : rclone: Version "v1.51.0" starting with parameters ["C:\\data\\rclone\\scripts\\rclone.exe" "sync" "b:\\en07.veaam_wasabi_20200607.144029\\EN07\\en07.veaamfull" "wasabieast2:vserver03\\en07.veaam\\rclone\\backup\\" "--stats=0" "--progress" "--s3-upload-concurrency=5" "--s3-chunk-size=256M" "--bind=192.168.62.233" "--backup-dir=wasabieast2:vserver03\\en07.veaam\\rclone\\archive\\20200607.144029\\" "--dry-run" "--log-level=DEBUG" "--log-file=C:\\data\\rclone\\logs\\en07.veaam_wasabi\\20200607.144029\\en07.veaam_20200607.144029_rclone.log"]
2020/06/07 14:40:34 DEBUG : Using RCLONE_CONFIG_PASS password.
2020/06/07 14:40:34 DEBUG : Using config file from "C:\\data\\rclone\\scripts\\rclone.conf"
2020/06/07 14:40:34 INFO : S3 bucket vserver03 path en07.veaam/rclone/backup: Waiting for checks to finish
2020/06/07 14:40:34 DEBUG : EN07/EN07.vbm: Sizes differ (src 6877863 vs dst 6815732)
2020/06/07 14:40:34 NOTICE: EN07/EN07.vbm: Not moving as --dry-run
2020/06/08 09:36:24 DEBUG : rclone: Version "v1.52.0" starting with parameters ["C:\\data\\rclone\\scripts\\rclone.exe" "sync" "b:\\en07.veaam_wasabi_20200608.093621\\EN07\\en07.veaamfull" "wasabieast2:vserver03\\en07.veaam\\rclone\\backup\\" "--stats=0" "--progress" "--s3-upload-concurrency=5" "--s3-chunk-size=256M" "--bind=192.168.62.233" "--backup-dir=wasabieast2:vserver03\\en07.veaam\\rclone\\archive\\20200608.093621\\" "--log-level=DEBUG" "--log-file=C:\\data\\rclone\\logs\\en07.veaam_wasabi\\20200608.093621\\en07.veaam_20200608.093621_rclone.log"]
2020/06/08 09:36:24 DEBUG : Using RCLONE_CONFIG_PASS password.
2020/06/08 09:36:24 DEBUG : Using config file from "C:\\data\\rclone\\scripts\\rclone.conf"
2020/06/08 09:36:24 DEBUG : fs cache: renaming cache item "b:\\en07.veaam_wasabi_20200608.093621\\EN07\\en07.veaamfull" to be canonical "//?/b:/en07.veaam_wasabi_20200608.093621/EN07/en07.veaamfull"
2020/06/08 09:36:24 DEBUG : fs cache: renaming cache item "wasabieast2:vserver03\\en07.veaam\\rclone\\backup\\" to be canonical "wasabieast2:vserver03/en07.veaam/rclone/backup"
2020/06/08 09:36:24 DEBUG : fs cache: renaming cache item "wasabieast2:vserver03\\en07.veaam\\rclone\\archive\\20200608.093621\\" to be canonical "wasabieast2:vserver03/en07.veaam/rclone/archive/20200608.093621"
1 Like
Here is the commit from 1.52..
committed 11:49AM - 01 May 20 UTC
Before this change we stored cached Fs under the config string the
user gave us. As the result of fs.ConfigString() can often...
ncw
(Nick Craig-Wood)
June 15, 2020, 3:50pm
9
This is an internal cache held in RAM for looking up names to remotes. You can ignore the debug message - it is just telling you that rclone stored the remote as a different name in the cache.
system
(system)
Closed
June 18, 2020, 3:50pm
10
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.