I’m wanting to run maintenance on my Kopia repo. I thought this was happening automatically. As it turns out, this is not the case. kopia maintenance run --full Running full maintenance... Looking for active contents... Processed 278 contents, discovered 1419... Processed 290 contents, discove…

What version of kopia are you using?

0.10.3 build: 902348191f96aae2dfb5ab909cbabad5b92cf229 from: kopia/kopia Edit: after posting this, I upgraded. I haven’t taken any further action until I hear back, but I’ve just installed this version, 0.12.1 build: 5227d74996b6520f9f96e4203cfe00b832a60d5f from: kopia/kopia

This repo is on a google drive. I just ran rclone dedupe kopia: --dedupe-mode newest against the entire repo. Now I’m trying the dangerous commands. (I used rclone to make an entire replica of the repo, so I won’t actually lose anything at any point by experimenting)

Well, this apparently doesn’t work. I used --advanced-commands=enabled and it went through. But now running kopia maintenance just tells me it had another error verifying some other string. Running multiple times, I get the same error with a different string. Boring. Time to try SAFETY=NONE or wh…

I have had similiar issues with 2 repositories. For 1 repository the issue magically solved itself after some time by upgrading. [image] Recovering from errors Support Where may I find documentation on how to recover from errors or atleast show some information on the dat…

How long did it take to solve itself? And did the other repository recover? I’m not sure what to do at this point. I’m considering mounting snapshots and snapping them to a new repo. Not sure about that yet. EDIT: Next I’m trying: count=25; while [ $count -ge 0 ]; do kopia maintenance --full | …

[image] Angler: How long did it take to solve itself? I don’t remember but I guess it shouldn’t take more than 2 days. It wasn’t a big deal for me as I had other backups (differnet software). Besides the maintenance error Kopia was working as usual. [image] Angler: And did the other repo…

I updated 5 days ago, and I haven’t had it self-correct. I read the whole story in the other thread a few days ago, maybe even before I posted this. It’s an annoying thread. Nobody seems to understand what you’re really asking. Side note, when a command finishes with no output, that’s typically a…

Okay, I’m having some success. I ran kopia snapshot fix invalid-files --commit and it gave me a ton of output. Now maintenance is running and I’m not getting those errors. Some interesting output it has now given: GC found 1654036 unused contents that are too recent to delete (427.2 GiB) GC foun…

Do I want to run dangerous commands? Cast your Vote here!

Support

dimejo December 29, 2022, 8:57am 6

I have had similiar issues with 2 repositories. For 1 repository the issue magically solved itself after some time by upgrading.

Topic		Replies	Views
Unable to perfom maintenance to reduce repo size Support	7	421	July 14, 2024
PLEASE READ: Don't use --safety=none for routine maintenance General	33	4034	March 25, 2025
Details of maintenance command Support	17	3029	June 16, 2025
Can not access repository, failed to get blob Support	17	4059	August 4, 2024
Unused blobs not being pruned Support	5	126	April 17, 2026

Do I want to run dangerous commands? Cast your Vote here!

Related topics