Started seeing lots of these messages this morning:
can’t remove temp file: remove /mnt/remotes/i5_750/kopia/pe8/09d/68685a1f1474aaafe2b8e5adc09-s56eaea7da1c0fc0b103.f.tmp.f675d9bfa5bdbade: no such file or directory
Should I be worried?
Thanks!
and now: error refreshing repository: error refreshing content index: error listing index blobs: error listing indexes: error listing n blobs: error listing blobs: error listing all blobs: error reading directory: readdirent /mnt/remotes/i5_750/kopia//n03: no such file or directory
some more errors:
async write error: unable to write content chunk 43697 of FILE:vdisk1.img: unable to write pack: error writing pack: can’t save pack data blob p1414a51148c694d8fe436bd679af657b-s6f444e17852534b9103: unable to complete PutBlobInPath:/mnt/remotes/i5_750/kopia/p14/14a/51148c694d8fe436bd679af657b-s6f444e17852534b9103.f despite 10 retries: unable to write pack: error writing pack: can’t save pack data blob p1414a51148c694d8fe436bd679af657b-s6f444e17852534b9103: unable to complete PutBlobInPath:/mnt/remotes/i5_750/kopia/p14/14a/51148c694d8fe436bd679af657b-s6f444e17852534b9103.f despite 10 retries
async write error: unable to write content chunk 43672 of FILE:vdisk1.img: unable to write pack: error writing pack: can’t save pack data blob pe34c17dc47afb8771a9a2e339a0e3304-s6f444e17852534b9103: unable to complete PutBlobInPath:/mnt/remotes/i5_750/kopia/pe3/4c1/7dc47afb8771a9a2e339a0e3304-s6f444e17852534b9103.f despite 10 retries: unable to write pack: error writing pack: can’t save pack data blob pe34c17dc47afb8771a9a2e339a0e3304-s6f444e17852534b9103: unable to complete PutBlobInPath:/mnt/remotes/i5_750/kopia/pe3/4c1/7dc47afb8771a9a2e339a0e3304-s6f444e17852534b9103.f despite 10 retries
At this point - I stopped the snapshot. Will reboot both the client on which the repo sits + will reboot the client trying to snapshot and see if this fixes it.
Wild guess - are you out of disk space?
Nope plenty of space… I ended up rebooting both the client and the repository and it worked. I wonder if just disconnecting from the repository on the problematic client would have worked. In any case, this was the first time I saw such errors.
I tested restore for that file, sha256sum matches both at the source (linux) and destination (windows) so I think I am good.
Is it a best practice to keep Kopia UI “connected” to the repository at all times (i.e. I have three windows clients with Kopia UI backing up to a single repository on a Windows Server box). I also have a linux client backing up to the same repository… perhaps the problem was that it needed to be reconnected?