[SOLVED] Lvm problem solved but not fully

[diaolin]

If i create an lvm-thin directly from interface on a new harddisk is all ok
until sometimes(sometimes), when i reboot the host, the volume doesn't come up
and i find with lvscan -a the thin *volume*_tmeta and _tdata ACTIVE and
with the command lvchange i cannot deactivate it.

THe problem: if i start a vm/ct that has a disk on this volume it says that the
_tmeta is already active.
Probed with many commands. Nothing to do.

This happened four times in four different clusters

Solved recreating manually the volume on a partition and not on the entire disk

Any hint?

Tx

 

[diaolin]

If i create an lvm-thin directly from interface on a new harddisk is all ok
until sometimes(sometimes), when i reboot the host, the volume doesn't come up
and i find with lvscan -a the thin *volume*_tmeta and _tdata ACTIVE and
with the command lvchange i cannot deactivate it.

THe problem: if i start a vm/ct that has a disk on this volume it says that the
_tmeta is already active.
Probed with many commands. Nothing to do.

This happened four times in four different clusters

Solved recreating manually the volume on a partition and not on the entire disk

Any hint?

Tx

It's clear that recreating the vm/ct is RECREATE and not resume.

If anyone has a hint i'm gratefully

Diaolin

 

[diaolin]

Anyone?

TX, i thought il was important

TX anyway

 

[fiona]

Hi,
this sounds similar to this thread and you might want to try the workaround mentioned there. But it's strange that deactivation doesn't work. Please post the full command and error message (please add -ddd to the command for some debug output).

 

[diaolin]

Hi,
this sounds similar to this thread and you might want to try the workaround mentioned there. But it's strange that deactivation doesn't work. Please post the full command and error message (please add -ddd to the command for some debug output).

Sorry, to much time from the error, i recreated the thin volumes

But if it happens can be that i post the screendump.

Anyway, this happens ONLY when i create the thin volume from the interface on the entire disk (unique method)

Manually creating thin volume (on a partition) does never happen (not to me)

pvcreate /dev/sdb1
and then prosecuting manual mode it works like a charme(always)

Tx anyway
Diaolin

 

[diaolin]

adopted the lvm.conf solution
but this is a partial solution.
thin_check_options = [ "-q", "--skip-mappings" ]
update-initramfs -u

Seems to be ok

Tx

 

[Tun Tun Aung]

adopted the lvm.conf solution
but this is a partial solution.
thin_check_options = [ "-q", "--skip-mappings" ]
update-initramfs -u

Seems to be ok

Tx

I tried above, but when i run " update-initramfs -u ", below message appear.
" No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. "
any help pls?

 

[fiona]

Hi,

I tried above, but when i run " update-initramfs -u ", below message appear.
" No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. "
any help pls?

if you are not using proxmox-boot-tool (see here), you can safely ignore this message.