Search results

Replace the disk with the proper procedure right? Osd out Osd down Osd destroy Osd create new one with new replaced disk. Is that correct way?

i got this error in my ceph status: pg 3.c is active+clean+inconsistent, acting [18,17,19] pg 3.d is active+clean+inconsistent, acting [16,17,19] pg 3.15 is active+clean+inconsistent, acting [18,19,17] after some search and investigate.. i notice this: root@c1:~# rados list-inconsistent-obj...

did u running "ceph pg repair" for your disk ? or just replace the disk then they will correct it

so there is no possible solution OS almalinux 9 with cpu type: kvm64 ? in the first page.. the solution is set cpu-type into "host". which i need "kvm64" obviously.

so right now almalinux 9 still cant running under cpu-type kvm64 ? it should be set to host ?

do u think this is issue with ceph itself? maybe using latest ceph version will be improved and no more locked like that? or maybe there is another think that i also dont know.

have u check this similar issue: https://bugzilla.proxmox.com/show_bug.cgi?id=1962

any solution for ceph storage? do u ever face similar issue in ceph got disk locked like this?

i am running on my own hardware. using modulegarden module https://www.modulesgarden.com/products/whmcs/proxmox-ve-vps yes i have talk with them, and they said the issue is about the proxmox itself: https://bugzilla.proxmox.com/show_bug.cgi?id=1962 but i think using some delay/sleep would be help.

i got this error as well trying to acquire csf lock 'storage-ceph-pool' during destroy the VM. is that the same solution using option --preallocation off ?

yes maybe need to put some sleep? how long should be? i notice about this option: Preallocation in this case we use cluster ceph. where Preallocation option located? and my case is not when create a new VM, but when destroy multiple VM in sequence.

helo i face this kind of problem last year.. but still dont get any solution. i have read this bug as well : https://bugzilla.proxmox.com/show_bug.cgi?id=1962 yes i am using module from modulegarden integrated with whmcs. when daily cron running and terminate the VM, sometime i got...

i think megabyte..

do we get solution for this case? yes i face this issue until now, running proxmox 7.4 yes i am using proxmox module from modulegarden latest version. this make the disk left as "orphan disk"

i face similar issue. remove VM xxx, the result vm-xx-cloudinit still exist there.. meanwhile vm-xx-disk-0 was removed successfully. so strange..any idea?

i face same problem in ubuntu 20.. after upgrade package and reboot..and result to kernel panic.. dont know why.

how to replicate this case.. i want to see the difference between that.. u said about manual allocating.. can u show me how do we create a new VM disk (manually) without create a new VM.. then i can try to remove another VM with checked "destroy unreferenced disk".. and see the result.. expected...

Fantastic, this option will correct any unrefences disk to be deleted..

Let say vm id 999 There are 1 disk attached and 1 disk deattach under vm 999. If we check “destroy unreferenced disks” , it means both disks will be destroyed? If we dont check, means only 1 attached disk will be destroyed?

if i check "Destroy unreferenced disks owned by guest" it means any VM disks that does not have VM ID (VM ID not exist but VM Disks ID still exist), it will be deleted as well?