Search results

@itNGO , Not that I have seen.

@mira is "a while" on the scale of weeks, or months?

It's a sad story unfortunately, I mucked about trying to get it working for months before finally giving up and accepting the data loss. :(

@mira , here you go! https://ceph.io/en/news/blog/2022/v17-2-0-quincy-released/ haha, my timing was close, only a couple of weeks off. lol

Snapshots are failing in the use case where a disk is added to a VM multiple times to increase throughput/parallelism via iothread and multipathd: Here is a relevant portion of the config Backups work well in this case, because the extra disk lines are set to backup=0, however, snapshotting...

When will proxmox be adding ceph quincy to the experimental repo? I accidentally upgraded to quincy near the start of the pandemic, struggled to get things working, but did become operational after a few weeks of mucking about. Can't rollback due to the structure changes, and have been waiting...

Hello, I am trying to enable Priority Flow Control (PFC) on my proxmox cluster with hopes to enable RoCEv2 on ConnectX-3 and ConnectX-4 HCA. This is a bit "in the weeds", but I am just a hobby user, so please bear with me as I am a little over my head here in some areas. Nvidia makes it...

pveceph mon create monmaptool: ../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. command 'monmaptool --clobber --addv rog '[v2:192.168.2.6:3300,v1:192.168.2.6:6789]' --print /tmp/monmap' failed: got signal 6 Haven't seen this error before...

This issue is periodically reoccurring for me as well. On my end, I've been stable for months, but this issue appeared at about the same time that a backup process was manually terminated, as it was running indefinitely on an unavailable cephfs.

Just reviving this old thread, as it appears that ceph has supported VDO devices since as far back as at least Mimic. See the bottom of the LVM flags documentation: Source: https://docs.ceph.com/en/mimic/dev/ceph-volume/lvm/ +1 on the feature request of VDO enabled OSD creation.

Closing the loop here. Watch closely for the bandwidth limits of the pcie gen 3 x4 slots, which were a limited factor in my system.

~1 month bump

Same issue here, was trying to setup a VM with 384GB memory, told to align to 8192 8192*48 = 393216 "TASK ERROR: memory size (393216) must be aligned to 8192 for hotplugging" dmidecode -t 16 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x1000, DMI type 16...

Very Probably Relevant: https://pve-devel.pve.proxmox.narkive.com/DOctgOiR/regression-with-latest-qemu-and-iothreads-option Going to test disabled iothread options

Probably Relevant: https://forum.proxmox.com/threads/how-can-i-debug-query-proxmox-support-failed-got-timeout-guest-startup-hangs-and-whole-pc-restarts.86593/ https://forum.proxmox.com/threads/warning-unable-to-connect-to-vm-100-socket-timeout-after-31-retries.20350/...

This sorta stuff pops up a lot on this node too: 400 Parameter verification failed. scsi10: hotplug problem - VM 130 qmp command 'query-pci' failed - unable to connect to VM 130 qmp socket - timeout after 31 retries at /usr/share/perl5/PVE/API2/Qemu.pm line 1459. (500)

Dredging up this old thread, as I am also experiencing similar issues. Have been for over a year, and only on a specific node. This node is unlike the rest of my hardware, with 48 cores, 96 threads (hyperthreading active), and ~700GB of memory. Becuase this issue only appears to occurr on this...

Well that was super tedious to figure out. For anyone who comes in future, my issue was with `/usr/bin/ceph-rbdnamer` which was missing for some stupid (User error) reason. udev is the system I was trying to identify. Other possible causes for this issue would be: Issues with user udev rules...

/dev/rbd1 kvm: -drive file=/dev/rbd/rbd/vm-150-disk-0,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap: Could not open '/dev/rbd/rbd/vm-150-disk-0': No such file or directory TASK ERROR: start failed: QEMU exited with code 1 I suspect this issue has...

Like a dummy I accidentally upgraded to the ceph dev branch (quincy?), and have been having nothing but trouble since. This wasn't actually intentionally, I was trying to implement a PR which was expected to bring my cluster back online after the upgrade to v& (and ceph pacific). --> It did...