Unable start any qube after forcefully canceling wyng backup

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_vols, monitor_only=False) File "/usr/local/bin/wyng", line 1786, in monitor_send tag = aset.Volume.Ses.tag_parse(tag_opt, delim=",") TypeError: tag_parse() missing 1 required positional argument: 'tag'

I try to send again without the tag flag.
I foolishly canceled the send because I wanted to do something else first.

when I start sudo wyng --dedup send again I get this error:
Preparing snapshots... Pairing snapshot for vm-and-dvm-private Traceback (most recent call last): File "/usr/local/bin/wyng", line 2977, in <module> monitor_send(datavols, selected_vols, monitor_only=False) File "/usr/local/bin/wyng", line 1761, in monitor_send = prepare_snapshots(selected if len(selected) >0 else datavols) File "/usr/local/bin/wyng", line 1283, in prepare_snapshots do_exec([[CP.lvm, "lvcreate", "-pr", "-kn", "-ay", "--addtag=wyng"] + tags File "/usr/local/bin/wyng", line 1154, in do_exec raise subprocess.CalledProcessError(err.returncode, err.args) subprocess.CalledProcessError: Command '['/sbin/lvm', 'lvcreate', '-pr', '-kn', '-ay', '--addtag=wyng', '--addtag=arch-71cb2590-3f10-40'-s', 'qubes_dom0/vm-and-dvm-private', '-n', 'vm-and-dvm-private.tock']' returned non-zero exit status 5.

I check /dev/qubes_dom0, and there seem to be some .tock volumes that i assume wyng created.
/tmp/wyng/err.log also says ‘vm-blablabla-private.tock’ already exists.

Since the .tock volume names seemed deterministic I just commented out this part of wyng:
do_exec([[CP.lvm, "lvcreate", "-pr", "-kn", "-ay", "--addtag=wyng"] + tags + ["--addtag=arch-"+aset.uuid, "-s", vgname+"/"+datavol, "-n",snap2vol]])
I clean up my wyng: sudo wyng --clean delete
Then I ran this command figuring that wyng would fix all the stuff:
ls /dev/qubes_dom0/ | grep -vPe '-(back|snap)$|^(root|swap)$|.tock$' | xargs -L1 sudo wyng add
I then uncommented the line in wyng again and added the rest of the volumes.
Adding went fine, but when I try to send with sudo wyng --dedup send, I get this error:
Pairing snapshot for vm-wws16-dl-dvm-private Pairing snapshot for vm-wws16-dl-private Pairing snapshot for vm-wws16-dl-root

Sending backup session 20221028-093515 to qubes://usb-guest-disp Send volume | vm-andoff-dvm-privateTraceback (most recent call last): File "/usr/local/bin/wyng", line 2977, in <module> monitor_send(datavols, selected_vols, monitor_only=False) File "/usr/local/bin/wyng", line 1822, in monitor_send dnew, dfreed = send_volume(datavol, localtime, ses_tags, send_all=datavol in send_alls) File "/usr/local/bin/wyng", line 1482, in send_volume with open(pjoin("/dev",aset.vgname,snap2vol),"rb", buffering=chunksize) as vf, \ FileNotFoundError: [Errno 2] No such file or directory: '/dev/qubes_dom0/vm-andoff-dvm-private.tock'

The .tock files are no longer in /dev/qubes_dom0/ and sudo lvscan shows a bunch of inactive .tock volumes, one for every regular -root/private volume.
I don’t know when this happened, but I can’t start any qube anymore, I always get this error:
Thin pool qubes_dom0-vm--pool-tpool (253:8) transaction_id is 9379, while expected 9380. Failed to suspend qubes_dom0/vm-pool with queued messages.

I haven’t tried any lv* commands yet out of fear. I also haven’t restarted or shut any qubes down.
Can I fix this? if not, will a regular qvm-backup backup created after the issue be fine to restore from?

1 Like

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.