Search results

Oh...sorry :D I didn't realized that 5.3 is a really new kernel :D I'm not that fit these days. I'll try this later, so thanks for the suggestions and help.

Well, maybe that was not clear. The client is not a guest running on the proxmox cluster. It is an old libvirt based host. And booting a newer kernel on this old CentOS...is not an option.

I think not, the client is a CentOS 6 with a 3.10 kernel ;)

Oh ok... I tried it with another command. Now there is a more verbose error. It seems that there is a feature mismatch. Maybe because of the older kernel version of the client. Is it a problem for proxmox to run the suggested command that disables object-map, fast-diff and deep-flatten? Or do...

Ok, thanks!

Ok, so there is no global changelog? For the whole distribution?

Are there any release notes for the patch releases? For example 6.0-9 to 6.0-11?

I need to copy some huge VMs. To reduce the downtime and the overall resources needed I want to mount the rbd image of a VM on the old host and dd it directly to the block device. Currently I'm not cappable of finding a way to mount an image created on the pve ceph cluster on another host. Is...

Interesting, just tried it again (third and a fourth time). And now it indeed does a live migration. Strange, maybe this was related to the problems I had with the node and why I tried to migrate the VMs from this node to another. So for the moment the question or problem seems solved. (Classic...

If I open the context menu for a node I have the option to migrate all VMs to another node in a bulk mode. This migration seems to be an offline migration as the VMs are just stopped and restarted on the new cluster node. Is it possible at the moment to do a bulk migration but in live mode, so...

Hey, we have some VMs on our old cluster (not proxmox, libvirt based) that we want to migrate to our new proxmox cluster. The VM storage used on the old cluster are lvm volumes. So what I need is a way to import these block devices to the new proxmox cluster using ceph as storage backend. Is...

The issue in the bugtracker says that it ignores the given size, this wasn't the case for me. Defining a value smaller than my disk size worked. My problem was that the behavior of auto mode and the failing of it isn't really understandable

Interesting, I'm 100% sure that I didn't need to define a size value with the 5.4 release and luminous.

Fixed it for now by defining the size manually. Is the need for this manual option something that changed with the upgrade to ceph nautilus?

Ok, I think I've solved the problem. This is a display problem only and it happens if your hostname is set to the FQDN instead of the local part only. After fixing this and rebooting the host the duplicate monitors and managers disappeared.

ceph versions: root@node5:~# ceph versions { "mon": { "ceph version 14.2.1 (9257126ffb439de1652793b3e29f4c0b97a47b47) nautilus (stable)": 3 }, "mgr": { "ceph version 14.2.1 (9257126ffb439de1652793b3e29f4c0b97a47b47) nautilus (stable)": 3 }, "osd": {}...

I have the same issue. Just wanted to create an OSD from a 6TB HDD with the DB/WAL on a 250GB SSD with the size set to auto. Didn't work. It falls back to the 10%/1% rule from the documentation. This isn't what I would expect from an "auto" mode.

Hey, I've a fresh proxmox 6.0.5 cluster installation with no changes beside cluster creation, installation of ceph (via gui), and the addition of two more monitors and managers (also via gui). The list under Ceph -> Monitor seems correct but in the overview every monitor and manager has a...