My current problem is this error (triggerable by running `lvm lvchange -ay 
-v qubes_dom0/vm-vault-personal-docs-private`)
It happens with some other affected vms.

    Activating logical volume qubes_dom0/vm-vault-personal-docs-private 
exclusively.
    activation/volume_list configuration setting not defined: Checking only 
host tags for qubes_dom0/vm-vault-personal-docs-private.
    Loading qubes_dom0-pool00_tdata table (253:2)
    Suppressed qubes_dom0-pool00_tdata (253:2) identical table reload.
    Loading qubes_dom0-pool00_tmeta table (253:1)
    Suppressed qubes_dom0-pool00_tmeta (253:1) identical table reload.
    Loading qubes_dom0-pool00-tpool table (253:3)
    Suppressed qubes_dom0-pool00-tpool (253:3) identical table reload.
    Creating qubes_dom0-vm--vault--personal--docs--private
    Loading qubes_dom0-vm--vault--personal--docs--private table (253:52)
  device-mapper: reload ioctl on (253:52) failed: No data available
    Removing qubes_dom0-vm--vault--personal--docs--private (253:52)


Btw, I've scanned through the files in /etc/lvm/archive. I wasn't sure if I 
should follow your advice there as that command requires --force to work 
with thin provisioning and I've seen warnings about this online. I see the 
files contain references to the volumes that lvs doesnt show.

I tested thin_check on qubes_dom0/pool00_meta0 volume (created by lvmodify 
--recover qubes_dom0), and get the following:
examining superblock
examining devices tree
   missing devices: [1, 747]
      too few entries in btree_node: 41, expected at least 42(max 
entries=126)

Running thin_check on meta1 and meta2 (created by running lvchange 
--recover qubes_dom0 a further 2 times) doesn't yield anything major:
examining superblock
examining devices tree
examining mapping tree
checking space map counts

I've followed a procedure to get a metadata snapshot (I couldn't directly 
access _tmeta using normal tools): https://serverfault.com/a/971620
and used thin_dump on the _meta0, _meta1, and _meta2 volumes created by 
`lvchange --recover`.

I diff'd the tmeta file against the others, and it seems only the first 
line is different?
1c1
< <superblock uuid="" time="640" transaction="2054" data_block_size="1024" 
nr_data_blocks="0">
---
> <superblock uuid="" time="640" transaction="2054" data_block_size="1024" 
nr_data_blocks="1842544">

so the pools tmeta has nr_data_blocks = 0.

Maybe my data is still there but the metadata is wrong?

On Monday, 29 July 2019 16:37:26 UTC, [email protected] wrote:

> Oh, forgive me, no not all vms are present in lvs. 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ac1978a4-68da-4960-bd69-8c4fdadd27ce%40googlegroups.com.

Reply via email to