After adding a new 1tb SSD to a proxmox server, have been having an unusual issue, hoping someone might have suggestions on where to go next.
Symptom is that if I try to clone or copy to this new lvm-thin volume, the transfer stalls out somewhere between 2 and 7 gb,
Syslog then gets filled with this:
the drive is showing in proxmox properly as an LVM-Thin
>pvs
...
/dev/sdf ssdthinvg lvm2 a-- 931.48g 51.16g
>lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
[...]
ssdthinpool ssdthinvg twi-aotz-- 850.00g 1.18 0.17
ssdthinpool_meta0 ssdthinvg -wi------- <10.11g
>vgs
VG #PV #LV #SN Attr VSize VFree
[...]
ssdthinvg 1 4 0 wz--n- 931.48g 51.16g
I've tried wiping the disk
I've tried it in a different bay in the chassis
Ive tried doing the LVM-thin setup via Proxmox
Ive tried setting up the LVM-thin via CLI
but every time, I get the same problem - when I try to Use the drive, device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
We have an identical drive, purchased at the same time, operating as an LVM volume on this same server, without issue... but no-go on getting this one to work as lvm-thin.
Any suggestions on how to move forward?
Symptom is that if I try to clone or copy to this new lvm-thin volume, the transfer stalls out somewhere between 2 and 7 gb,
Syslog then gets filled with this:
Code:
Apr 19 15:43:42 proxmox1 kernel: [1488991.160799] device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
Apr 19 15:43:43 proxmox1 kernel: [1488991.407883] device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
Apr 19 15:43:43 proxmox1 kernel: [1488991.409345] device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
Apr 19 15:43:43 proxmox1 kernel: [1488991.409810] device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
Apr 19 15:43:43 proxmox1 kernel: [1488991.410306] device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
the drive is showing in proxmox properly as an LVM-Thin
>pvs
...
/dev/sdf ssdthinvg lvm2 a-- 931.48g 51.16g
>lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
[...]
ssdthinpool ssdthinvg twi-aotz-- 850.00g 1.18 0.17
ssdthinpool_meta0 ssdthinvg -wi------- <10.11g
>vgs
VG #PV #LV #SN Attr VSize VFree
[...]
ssdthinvg 1 4 0 wz--n- 931.48g 51.16g
I've tried wiping the disk
I've tried it in a different bay in the chassis
Ive tried doing the LVM-thin setup via Proxmox
Ive tried setting up the LVM-thin via CLI
but every time, I get the same problem - when I try to Use the drive, device-mapper: thin: dm_thin_get_highest_mapped_block returned -5
We have an identical drive, purchased at the same time, operating as an LVM volume on this same server, without issue... but no-go on getting this one to work as lvm-thin.
Any suggestions on how to move forward?