Verify an rclone transfer with checksums

Compare a completed rclone WebDAV transfer by downloaded bytes, record missing or differing paths, and treat a clean command exit as one check.

Last reviewed

A successful copy summary is not a byte comparison. For the released Dosya WebDAV workflow, use a separate local destination and rclone check --download so the generic other backend reads content instead of assuming a compatible remote hash.

Four-step workflow for preserving both paths, running a downloaded-byte comparison, capturing mismatch status, and verifying one downloaded file.
Four-step workflow for preserving both paths, running a downloaded-byte comparison, capturing mismatch status, and verifying one downloaded file. Open full-size screenshot.

Steps

  1. Save the exact source and destination used by the completed transfer, including whether an ordinary remote needs the All/ prefix or an anchored remote exposes its folder directly.
  2. List both trees recursively and preserve the output before checking: rclone lsf ./sample-source --recursive and rclone lsf dosya-webdav:All/rclone-checks --recursive.
  3. Run a read-only comparison: rclone check ./sample-source dosya-webdav:All/rclone-checks --download.
  4. Add --one-way only when destination-only files are expected and should not count as errors. Do not use it to hide source files missing at the destination.
  5. Read every missing, differing and unreadable path, then capture the immediate process status with echo $? or PowerShell’s $LASTEXITCODE.
  6. Verify one downloaded file before removing its local source. The --download check rereads remote bytes and consumes allowance.

Dosya WebDAV can expose dates, ETags and a stored SHA-256 property, but the generic other backend does not guarantee a full compatible hash comparison. The explicit download comparison does not modify either tree.

Reference for “Verify an rclone transfer with checksums”: Dosya rclone overview page.
Reference for “Verify an rclone transfer with checksums”: Dosya rclone overview page. Open full-size screenshot.

Expected result

The check exits cleanly only when every required source path has matching destination bytes. Expected destination-only items are ignored only when --one-way was deliberately selected, and all mismatches remain recorded for repair.

HTTP 401, 403, 404, 423 and 429 failures are verification failures, not content matches. Resolve credential, permission, path, lock or Retry-After conditions before rerunning the check.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.