What is the problem you are having with rclone?
I suspect I have detected a bug when using "combine". I have checked other reports in the forum and the closest seems to be this one from 2023, which claims to be solved:
When reading the content of a folder in a combine, the results are different depending on whether a "/" is placed after ":" or not. This problem does not happen for the root folder.
In practice:
rclone ls combineremote:folder works
rclone ls combineremote:/folder does not work
However accessing directly the individual remote that is part of the combine, with or without ":/" works as expected.
I found this problem with two different combines, one based on google drive crypted remotes, the other based on koofr nonrmal (unencrypted) remotes. Same behaviour with both of them.
For simplicity, I only describe below (according to the bug reporting template) the behaviour with the koofr combine and with "rclone ls", but I have the same problem with other commands with any of both combines.
In my tests, examples of specific commands that work without issues are:
rclone copy $HOME/dir/Backup backupkf:Backup # access to combine folder without ":/"
rclone copy $HOME/dir/Backup kfd2:/Backup # access to remote folder (not via combine) with ":/"
rclone copy $HOME/dir/Backup kfd2:Backup # access to remote folder (not via combine) without ":/"
rclone ls backupkf:/ # access to a combine root with ":/"
rclone ls backupkf: # access to combine root without ":/"
rclone ls backupkf:Backup # access to combine folder without ":/"
rclone ls kfd2:/Backup # access to remote folder (not via combine) with ":/"
rclone ls kfd2:Backup # access to remote folder (not via combine) without ":/"
Examples of commands that do not work (error : "Bad object: file not under root") are:
rclone copy $HOME/dir/Backup backupkf:/Backup # access to combine folder with ":/"
rclone ls backupkf:/Backup # access to combine folder with ":/"
Run the command 'rclone version' and share the full output of the command.
Running the confirmed latest version of rclone (checked at Rclone downloads):
rclone v1.67.0
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 6.8.0-40-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.4
- go/linking: static
- go/tags: none
Tested also with the latest beta:
rclone v1.68.0-beta.8241.0e5eb7a9b
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 6.8.0-40-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.0
- go/linking: static
- go/tags: none
The behaviour in both seems the same, for the rest of this report, I came back to the latest stable version:
sudo rclone selfupdate
2024/08/25 18:38:11 NOTICE: Successfully updated rclone from version v1.68.0-beta.8241.0e5eb7a9b to version v1.67.0
Which cloud storage system are you using? (eg Google Drive)
Issue tested with two clouds: Koofr and Google drive. The feedback below belongs to Koofr
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone ls backupkf:/Backup
The rclone config contents with secrets removed.
[koofr]
type = koofr
user = xxxx
password = xxxx
[kfr1]
type = koofr
provider = koofr
user = xxxx
password = xxxx
[kfd2]
type = koofr
provider = koofr
user = xxxx
password = xxxx
[kfe3]
type = koofr
provider = koofr
user = xxxx
password = xxxx
[backupkf]
type = combine
upstreams = Adir=kfe3:Adir Gdir=koofr:Gdir Rdir=kfr1:Rdir Tdir=kfd2:Tdir Backup=kfd2:Backup
A log from the command with the -vv flag
2024/08/25 18:57:57 DEBUG : rclone: Version "v1.67.0" starting with parameters ["rclone" "ls" "backupkf:/Backup" "-vv" "--log-file=/home/xxxx/kk" "-vv"]
2024/08/25 18:57:57 DEBUG : Creating backend with remote "backupkf:/Backup"
2024/08/25 18:57:57 DEBUG : Using config file from "/home/xxxx/.config/rclone/rclone.conf"
2024/08/25 18:57:57 DEBUG : Creating backend with remote "kfd2:Backup"
2024/08/25 18:57:57 DEBUG : Creating backend with remote "kfd2:Tdir"
2024/08/25 18:57:57 DEBUG : Creating backend with remote "koofr:Gdir"
2024/08/25 18:57:57 DEBUG : Creating backend with remote "kfe3:Adir"
2024/08/25 18:57:57 DEBUG : Creating backend with remote "kfr1:Rdir"
2024/08/25 18:57:57 ERROR : dos.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : dos.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : uno.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : uno.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : uno.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : dos.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : dos.txt: Bad object: file not under root
2024/08/25 18:57:57 ERROR : uno.txt: Bad object: file not under root
2024/08/25 18:57:57 DEBUG : 5 go routines active