Restic prune & HDD full

I run restic prune and this occurs

will remove 0 invalid files
will delete 0 packs and rewrite 865 packs, this frees 2.017 GiB
Save(<data/68d998c393>) returned error, retrying after 575.330471ms: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 951.056359ms: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 804.667193ms: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 1.525443181s: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 1.907970118s: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 5.395378437s: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 3.8871659s: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 9.67611114s: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 17.628583768s: server response unexpected: 400 Bad Request (400)
Save(<data/68d998c393>) returned error, retrying after 14.776301542s: server response unexpected: 400 Bad Request (400)
server response unexpected: 400 Bad Request (400)
github.com/restic/restic/internal/backend/rest.(*Backend).Save
	github.com/restic/restic/internal/backend/rest/rest.go:150
github.com/restic/restic/internal/backend.(*RetryBackend).Save.func1
	github.com/restic/restic/internal/backend/backend_retry.go:56
github.com/cenkalti/backoff.RetryNotify
	github.com/cenkalti/backoff/retry.go:37
github.com/restic/restic/internal/backend.(*RetryBackend).retry
	github.com/restic/restic/internal/backend/backend_retry.go:36
github.com/restic/restic/internal/backend.(*RetryBackend).Save
	github.com/restic/restic/internal/backend/backend_retry.go:50
github.com/restic/restic/internal/cache.(*Backend).Save
	github.com/restic/restic/internal/cache/backend.go:54
github.com/restic/restic/internal/repository.(*Repository).savePacker
	github.com/restic/restic/internal/repository/packer_manager.go:106
github.com/restic/restic/internal/repository.(*Repository).SaveAndEncrypt
	github.com/restic/restic/internal/repository/repository.go:270
github.com/restic/restic/internal/repository.(*Repository).SaveBlob
	github.com/restic/restic/internal/repository/repository.go:704
github.com/restic/restic/internal/repository.Repack
	github.com/restic/restic/internal/repository/repack.go:87
main.pruneRepository
	github.com/restic/restic/cmd/restic/cmd_prune.go:278
main.runPrune
	github.com/restic/restic/cmd/restic/cmd_prune.go:85
main.glob..func18
	github.com/restic/restic/cmd/restic/cmd_prune.go:25
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra/command.go:762
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra/command.go:850
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra/command.go:800
main.main
	github.com/restic/restic/cmd/restic/main.go:86
runtime.main
	/usr/lib/go-1.12/src/runtime/proc.go:200
runtime.goexit
	/usr/lib/go-1.12/src/runtime/asm_amd64.s:1337

No problem for me, solved the problem. Just letting you know, because I don’t think it’s supposed to happen like this.

When reporting a problem, please include all relevant information, such as the restic version, what backend you use, the version of the backend software in case you run it yourself, the entire command you ran, and so on. Otherwise we have to make a lot of guesses and that’s never fruitful in debugging a problem.

Client

restic 0.9.6 compiled with go1.12.12 on linux/amd64

Restic Server

restic 0.9.6 compiled with go1.13.4 on linux/amd64

Command

restic --password-file /root/passwd -r rest:https://$USER:$PASSWORD@<IP>:8000/data prune

Thanks. Although the rest-server version doesn’t seem right - it should say “rest-server” and not restic, can you check that version again?

I am thinking that if the rest-server replied with a 400 HTTP code, it should say something in its logs. Can you check those to see what it says?

Uups, ok here version from rest-server

rest-server 0.9.7 (v0.9.8-24-gfd635e3) compiled with go1.11.6 on linux/amd64