jthornber
commented
1 year ago If you pack the metadata with thin_metadata_pack from the latest thinp tools I'll take a look.
- Joe
On Thu, 2 Mar 2023 at 09:26, deetwelve @.***> wrote:
Recently I had an issue where my lvm would not mount. After some long days researching this topic. I eventually stumbled upon your tools via someones blog.
I initially ran:
lvconvert --repair pve/data
All I ever get is a repeated "Manual repair required!" message. I don't think it ever does anything. However whenever I reboot the server and it runs the repair. I am greeted with the same message underneath it that "Manual repair required!" but I see this below that for about 5 seconds before it loads proxmox. The part specially that states the clean blocks.
Found volume group "pve" using metadata type lvm2 Check of pool pve/data failed (status:1). Manual repair required! 2 logical volume(s) in volume group "pve" now active /dev/mapper/pve-root: clean, 58394/6291456 files, 5463211/25165824 blocks
I tried to make sense of this and am now stuck here.
Ran lvchange -ay pve/data_tmeta the following in readonly:
TRANSACTION_ID=10 METADATA_FREE_BLOCKS=3918308 Checking thin metadata device details tree device details tree: node error: checksum error AgTL5iMA, effecting keys [..]
Additional information if any of this is helpful:
fdisk -l
Disk /dev/sda: 1.36 TiB, 1499832039424 bytes, 2929359452 sectors Disk model: LOGICAL VOLUME Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 262144 bytes / 1310720 bytes Disklabel type: gpt Disk identifier: A3A2F44C-5D01-4566-9F1D-A0474AA28060
Device Start End Sectors Size Type /dev/sda1 2560 5119 2560 1.3M BIOS boot /dev/sda2 5120 1054719 1049600 512.5M EFI System /dev/sda3 1054720 2929357454 2928302735 1.4T Linux filesystem
Disk /dev/sdb: 16.37 TiB, 18003355459584 bytes, 35162803632 sectors Disk model: LOGICAL VOLUME Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 262144 bytes / 1572864 bytes Disklabel type: gpt Disk identifier: 6B0CC303-8D66-4D65-90DE-196D9B7C90AA
Device Start End Sectors Size Type /dev/sdb1 34 2047 2014 1007K BIOS boot /dev/sdb2 2048 1050623 1048576 512M EFI System /dev/sdb3 1050624 35162803598 35161752975 16.4T Linux LVM
Disk /dev/loop0: 673.75 MiB, 706473984 bytes, 1379832 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
pvs -a
PV VG Fmt Attr PSize PFree /dev/sda2 --- 0 0 /dev/sda3 --- 0 0 /dev/sdb2 --- 0 0 /dev/sdb3 pve lvm2 a-- 16.37t <16.38g
vgs -a
VG #PV #LV #SN Attr VSize VFree
pve 1 9 0 wz--n- 16.37t <16.38g
lvs -a
data pve twi---tz-- <16.23t
[data_tdata] pve Twi------- <16.23t
[data_tmeta] pve ewi------- 15.81g
[lvol0_pmspare] pve ewi------- 15.81g
root pve -wi-a----- 96.00g
swap pve -wi-a----- 8.00g
vm-100-disk-0 pve Vwi---tz-- 500.00g data
vm-101-disk-0 pve Vwi---tz-- 5.00t data
vm-102-disk-0 pve Vwi---tz-- 500.00g data
vm-103-disk-0 pve Vwi---tz-- 5.00t data
vm-104-disk-0 pve Vwi---tz-- 100.00g data
vm-105-disk-0 pve Vwi---tz-- 16.00t data
pvscan
PV /dev/sdb3 VG pve lvm2 [16.37 TiB / <16.38 GiB free]
Total: 1 [16.37 TiB] / in use: 1 [16.37 TiB] / in no VG: 0 [0 ]
lvscan
inactive '/dev/pve/data' [<16.23 TiB] inherit
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [96.00 GiB] inherit
inactive '/dev/pve/vm-100-disk-0' [500.00 GiB] inherit
inactive '/dev/pve/vm-101-disk-0' [5.00 TiB] inherit
inactive '/dev/pve/vm-102-disk-0' [500.00 GiB] inherit
inactive '/dev/pve/vm-103-disk-0' [5.00 TiB] inherit
inactive '/dev/pve/vm-104-disk-0' [100.00 GiB] inherit
inactive '/dev/pve/vm-105-disk-0' [16.00 TiB] inherit
vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 31
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 9
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 16.37 TiB
PE Size 4.00 MiB
Total PE 4292205
Alloc PE / Size 4288013 / <16.36 TiB
Free PE / Size 4192 / <16.38 GiB
VG UUID FwXD4j-Y1q4-DyV0-i34b-qGSw-zwAO-2aHh2f
Thank you very much for your time just reading this and also any help. It's much appreciated.
— Reply to this email directly, view it on GitHub https://github.com/jthornber/thin-provisioning-tools/issues/252, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABOSQ6QLQEDVA5DDV6WOA3W2BRV3ANCNFSM6AAAAAAVNDY5OY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
deetwelve
mingnus
Recently I had an issue where my lvm would not mount. After some long days researching this topic. I eventually stumbled upon your tools via someones blog.
I initially ran:
All I ever get is a repeated "Manual repair required!" message. I don't think it ever does anything. However whenever I reboot the server and it runs the repair. I am greeted with the same message underneath it that "Manual repair required!" but I see this below that for about 5 seconds before it loads proxmox. The part specially that states the clean blocks.
I tried to make sense of this and am now stuck here.
Ran lvchange -ay pve/data_tmeta the following in readonly:
Additional information if any of this is helpful:
fdisk -l
pvs -a
vgs -a
lvs -a
pvscan
lvscan
vgdisplay
Thank you very much for your time just reading this and also any help. It's much appreciated.