Write: broken pipe -- files gone to ghost town?

Hey!

~new to restic~

I was running restic, sent it to bg (ctrl+z) and shortly back to fg (10-15s). I got the following error. What happens to the files as they are not yet in a snapshot? (Well I know they got uploaded, but is there any way to “clean” the repo?)

[1:08:04] 57.99%  8.978 MiB/s  35.813 GiB / 61.763 GiB  344959 / 661703 items  0 errors  ETA 49:20
error while saving data to the repo: Put [S3-bucket-stuff]: net/http: HTTP/1.x transport connection broken: write tcp [MY-IP]:55256->[AWS-IP]:443: write: broken pipe
client.PutObject
github.com/restic/restic/internal/backend/s3.(*Backend).Save
	src/github.com/restic/restic/internal/backend/s3/s3.go:228
github.com/restic/restic/internal/repository.(*Repository).savePacker
	src/github.com/restic/restic/internal/repository/packer_manager.go:122
github.com/restic/restic/internal/repository.(*Repository).SaveAndEncrypt
	src/github.com/restic/restic/internal/repository/repository.go:203
github.com/restic/restic/internal/repository.(*Repository).SaveBlob
	src/github.com/restic/restic/internal/repository/repository.go:529
github.com/restic/restic/internal/archiver.(*Archiver).Save
	src/github.com/restic/restic/internal/archiver/archiver.go:104
github.com/restic/restic/internal/archiver.(*Archiver).saveChunk
	src/github.com/restic/restic/internal/archiver/archiver.go:161
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:2337
panic: client.PutObject: Put [S3-bucket-stuff]: net/http: HTTP/1.x transport connection broken: write tcp [MY-IP]:55256->[AWS-IP]:443: write: broken pipe

goroutine 353448 [running]:
github.com/restic/restic/internal/archiver.(*Archiver).saveChunk(0xc420207ef0, 0xdff020, 0xc4200160b8, 0x1e46b247, 0xefdaf, 0x188f18b5900000, 0xc5e872e000, 0xefdaf, 0x5dc000, 0xc42009e2c0, ...)
	src/github.com/restic/restic/internal/archiver/archiver.go:166 +0x41b
created by github.com/restic/restic/internal/archiver.(*Archiver).SaveFile
	src/github.com/restic/restic/internal/archiver/archiver.go:240 +0x3d0

Hey, welcome to the forum!

When you abort a backup (or restic aborts, after it was interrupted), there will probably be incomplete files in the repo. These will be cleanup up by the next run of restic prune.