Hi guys I recently tried to start using wyng to back up some qubes. I try to send with sudo wyng --dedup --tag=init send. I initally got a python error because of tags: Traceback (most recent call last): File "/usr/local/bin/wyng", line 2977, in <module> monitor_send(datavols, selected_vol…

[image] FudgingDonut: transaction_id is 9379, while expected 9380 [image] Hard shutdown broke my system User Support After a hard shutdown, my Qubes OS 4.1 has broken. It did not allow me to start any VMs with the error something like with different numbers. Afte…

I ended up restoring a backup taken after the issue appeared, which worked.

If it needs to be said, a backup tool should never potentially compromise data. I never presume to speak for the Qubes team. When I comment in the Forum or in the mailing lists I speak for myself.

@tasket I switched to Wyng a couple of days ago and ran into the same issue. This broke my system. What happened: I was running wyng ... send. It was going for a full rescan even while I didn’t specify “–remap”, and had successfully backed up minutes before. I Ctrl+C killed it without thinking. F…

Just do be sure: did you just wyng ... receive a previous snapshot? I assume you meant “restoring a backup taken before the issue appeared”.

@fujack @FudgingDonut This type of failure seems endemic on Qubes and stems from Thin LVM storage metadata becoming overtaxed and/or corrupt. It can be triggered by using Qubes or Wyng, since they both create/delete snapshots as part of their normal operation. The severity of the problem can also…

▶ off-topic, personal response to unman's post

Ok, so that was a weird ride. First of all thank you for the fast & complete answer: immensely helpful. I was not able to remove any snapshot or run lvconvert --repair because of that same error: Thin pool qubes_dom0-vm--pool-tpool (253:8) transaction_id is 16242, while expected 16243. Failed …

Wyng is creating a series of volume snapshots along with a metadata snapshot, and it will tend to do this in the same pattern each time you run wyng send since it sorts the volume list by name. So there is likely a lingering inconsistency/corruption in your LVM thin pool that is triggered by this s…

So, what I ended up doing was to delete my previous wyng backups and the /var/lib/wyng directory, and to start over. This went fine, so I suspect wyng was doing something specific that triggered the lvm failure. However I can’t tell whether the issue was related to a lack of space. IIRC the highest…

Unable start any qube after forcefully canceling wyng backup

User Support

enmus October 28, 2022, 8:21pm 2