Note that because the below sequence was generated after an original sync operation, the volume reported as having been transferred is not representative of the size of the stores.
$ rclone sync <endpoint-alias>:<src-bucket-name> <endpoint-alias>:<dst-bucket-name> --progress --fast-list
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Checks: 10224 / 10224, 100%
Elapsed time: 25.6s
$
$ rclone check <endpoint-alias>:<src-bucket-name> <endpoint-alias>:<dst-bucket-name> --progress --fast-list
2026-11-06 03:29:03 NOTICE: S3 bucket <dst-bucket-name>: 0 differences found
2026-11-06 03:29:03 NOTICE: S3 bucket <dst_bucket-name>: 10224 matching files
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Checks: 10224 / 10224, 100%
Elapsed time: 1.6s
What is the problem you are having with rclone?
The hosting infrastructure reports an object count for the source bucket that is one greater than the count acquired by the destination bucket, following the sync operation in rclone. The lower account is reported both by output of rclone, and also by the infrastructure.
Further, it remains robust over repeated iterations of sync and check.
Seemingly, one object is being consistently lost in the copy operation.
In the particular case, for example, rclone reports an object count of 10224, whereas the infrastructure reports the same count only for the destination bucket. The source bucket is reported as having an object count one greater.
Therefore, it should be questioned whether rclone is producing a complete copy of the source.
It is important to identify a process to verify the validity of the copy results, and it is also important to account for the anomalous object counts.
Run the command 'rclone version' and share the full output of the command.
rclone v1.60.1-DEV
- os/version: debian 13.7 (64 bit)
- os/kernel: 6.12.113+deb13-amd64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.2
- go/linking: dynamic
- go/tags: none
Which cloud storage system are you using? (eg Google Drive)
S3
The command you were trying to run (eg rclone copy /tmp remote:tmp)
-
rclone sync <endpoint-alias>:<src-bucket-name> <endpoint-alias>:<dst-bucket-name> --progress --fast-list -
rclone check <endpoint-alias>:<src-bucket-name> <endpoint-alias>:<dst-bucket-name> --progress --fast-list
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
Usage:
rclone config [flags]
rclone config [command]
Available Commands:
create Create a new remote with name, type and options.
delete Delete an existing remote.
disconnect Disconnects user from remote
dump Dump the config file as JSON.
file Show path of configuration file in use.
password Update password in an existing remote.
paths Show paths used for configuration, cache, temp etc.
providers List in JSON format all the providers and options.
reconnect Re-authenticates user with remote.
show Print (decrypted) config file, or the config for a single remote.
touch Ensure configuration file exists.
update Update options in an existing remote.
userinfo Prints info about logged in user of remote.
Flags:
-h, --help help for config
Additional help topics:
rclone config edit Enter an interactive configuration session.
Use "rclone [command] --help" for more information about a command.
Use "rclone help flags" for to see the global flags.
Use "rclone help backends" for a list of supported services.
Command config needs 0 arguments maximum: you provided 1 non flag arguments: ["redacted"]
The version in use is the most recent available through the official repositories of Debian 13 (Trixie). Unfortunately, installation of a more recent version is not feasible.
A log from the command that you were trying to run with the -vv flag
The verbose output is extremely long, and also inclusive of data that cannot be shared publicly.
Hopefully, the basic output, along with the explanations, would be sufficient for discussing a resolution. If they prove inadequate, then I would be agreeable to considering a means of providing a redacted version of the output.