Search results

We had a power outage yesterday. For unrelated reasons, 4/5 of the nodes did not power up successfully. As I powered them up, I would fix each node, which added maybe 5 minutes to each node's bootup. After this, I started seeing these messages constantly on all nodes but _only_ for the secondary...

So this is now solved, I think. According to my error log, it seems like, somehow, an MDS was reporting an older version than 16.2.7. Checking the CephFS section in the Proxmox web UI, I actually had 2 MDSes that were reporting _no_ version string at all. I first did ceph mds fail...

I've posted a message to the ceph mailing list here: https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/FU6JPZNLY2PVF4ZV7PYP2KDJ4UFSVOR2/

Yup, I can confirm. Tried to turn it off this morning and I still get assertion failures. I wonder if I can delete and re-create each mon one at a time...

Did you upgrade all of your nodes?

I'm having this happen now as well, I think you're supposed to switch it back after the upgrade to the mon db is done but I don't know how to tell when that happens?

For the past few years I've been gaming on a Windows 10 VM with a GTX 1070 Ti. This has been working surprisingly well. After upgrading to Proxmox 7.0, the VM is now chugging seemingly randomly. I can play for an hour or two fine but then suddenly, I'll start getting "skips" for about half...

Created a bug here, please let me know if there's anything else I can do: https://bugzilla.proxmox.com/show_bug.cgi?id=3616

I recently upgraded to Proxmox 7 and Ceph Pacific which brought multiple CephFS support. My goal was to create one FS on my HDD OSDs and one FS on my SSD OSDs so I can balance workloads across the two sets of hardware. I have a "performance" and "capacity" crush rule. Previously, I had 2 RBD...

Wow ok, so there apparently is indeed a "110/vm-110-disk-0.qcow2" in that directory back from November. I guess it didn't get deleted. I'm assuming it didn't list it because the storage doesn't support images. Moving that disk out of the way allowed the migration to continue. Would you consider...

Whoops, I forgot to run that as root, here's the actual output: Use of uninitialized value $node in concatenation (.) or string at /usr/share/perl5/PVE/Storage.pm line 145, <DATA> line 755. Use of uninitialized value $node in concatenation (.) or string at /usr/share/perl5/PVE/Storage.pm line...

Yeah, that's what I was thinking too, it seems very strange. When I run that I get "storage 'local-zfs' does not exist". Is there a way to increase debug output during that migration?

pveversion -v: proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve) pve-manager: 6.1-11 (running version: 6.1-11/f2f18736) pve-kernel-helper: 6.1-9 pve-kernel-5.3: 6.1-6 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-5.3.18-2-pve: 5.3.18-2 ceph: 14.2.9-pve1 ceph-fuse: 14.2.9-pve1 corosync...

I have four nodes setup with Ceph, one of which _also_ has ZFS setup. All of my ISOs, etc. are on ZFS. This particular VM was running on a node _without_ ZFS, just Ceph. I had to take that node offline today so I migrated it to the one _with_ ZFS. After bringing the node back up, I cannot...

I'm having a similar issue. I have a single node with a ZFS RAIDZ that is used only by that node for a handfull of VMs and CTs; it's not marked as shared, and only set on that node.. I have 3 additional nodes with all 4 sharing a Ceph RBD pool. I created a VM on this NAS Node during an upgrade...

It is indeed an SELinux issue, the following policy solved this for me: module fedora_proxmox 1.0; require { type virt_qemu_ga_t; type systemd_logind_t; class dbus { send_msg }; } allow virt_qemu_ga_t systemd_logind_t:dbus send_msg; allow systemd_logind_t virt_qemu_ga_t:dbus...

Yeah, everything in there is owned by ceph. Interestingly, so was the block device. I saw similar problems with other kinds of block devices so I'm willing to accept this being a problem with upstream for the moment.

Ah, I see. You're correct. Since https://pve.proxmox.com/wiki/Ceph_Jewel_to_Luminous was geared towards 4.4, it simply asks you to replace "jewel" with "luminous". The 4.4 to 5.0 upgrade guide at https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0 does tell you to replace the Ceph repos with...

I just upgraded my cluster to Proxmox 5.1 and am trying to upgrade one of the Ceph OSDs to Bluestore. I've shut down and removed the old OSD completely. From the crush map, auth, and the cluster: cluster: id: 2b70b442-d912-4d6b-b9ad-b359b9339e4f health: HEALTH_WARN...

Ah hah, while I wasn't doing that originally, in responding to your comment I noticed that I forgot to switch ceph's repo to stretch. Whoops. That fixed the issue.