rclone backend restore - documentation regression

[Anthchirp]

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/cant-restore-files-from-aws-glacier-deep-only-directories/39258/10

What is the problem you are having with rclone?

The rclone documentation lost the fix in #7077 at some point.
The underlying issue is still the same, so the fix PR just needs reapplying.

What is your rclone version (output from rclone version)

rclone v1.69.1
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.0-1071-raspi (aarch64)
- os/type: linux
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.24.0
- go/linking: static
- go/tags: none

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

linux, 64 bit

Which cloud storage system are you using? (e.g. Google Drive)

AWS S3

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

rclone backend restore awss3:bucket/path/object

A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)

2025/03/09 01:25:01 DEBUG : rclone: Version "v1.69.1" starting with parameters ["rclone" "-vv" "backend" "restore" "awss3:bucket/path/object"]
2025/03/09 01:25:01 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2025/03/09 01:25:01 DEBUG : 5 go routines active
2025/03/09 01:25:01 NOTICE: Failed to backend: is a file not a directory

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

[kapitainsky]

Indeed somebody edited it out by mistake. Feel free to submit docs correction PR.

Maintaining up to date documentation is never ending task and is impossible without community watchful eyes and contributions.

[ncw]

Well spotted @Anthchirp

I see the problem. The edits were made to an auto generated part of s3.md - they should have been made in backend/s3/s3.go which is the source.

We should probably make a linter for this.

That is my bad for not spotting that in the review.

Do you want to send a PR with the change applied to s3.go?

[Anthchirp]

👍
Done