Search results

First I tried this, but I found out later they weren't persistent: echo eth >/sys/bus/pci/devices/0000:XX:00.0/mlx4_port1 echo eth >/sys/bus/pci/devices/0000:XX:00.0/mlx4_port2 It's not just not persistent through reboots, or ifdowns. Basically for drivers on linux, you install the Mellanox...

Did you ever find another way to change this permanently?

So for the record everyone, as I couldn't get the monitors or osds to bind to more than one address (IPv6 or IPv4), we simply created some static routes on the standalone host, it that enabled it to reach the segregated subnet that ceph is on. Of course first we had to have IPv6 addresses on...

From what I can see, the monitors and osds only bind to one address, no matter what you put in there.

Man I wish this thread went longer. I'm having the same issue. Any luck @b2a225 ?

So I tried just another IPv6 subnet, but still no luck.

Oh okay. I will look into how to go about routing it.

Hello. To help make migration much easier, I'd like to connect a standalone node I have to the Proxmox managed ceph storage on a three node cluster by adding that storage as RBD on the standalone. The issue is, the current ceph public_network is isolated, because it's directly attached 40G NICs...

Worked for me too. Thank you! @FloUhl and @Gilberto Ferreira !

This seemed to do the trick for me as well. Thank you for sharing!

Hello all, We're looking for Best Practices regarding setting IOPS and Throughput limits on "Hard Disks" in proxmox. There's obviously limit and brust settings under Advanced on a given disk. Questions we have: Is there a way to see, from the Host level, the current IOPS/Throughput a...

This worked for me too thank you!! (had to restart after too, or only worked with rbd tool in cli)

So we had this problem again, with the same setup as described at the start of this thread, but while live migrating a VM that didn't have discard set :/ The only thing I could find worth noting was that this VM did not have "format=raw", as mentioned in the bug referenced above. What happened...

Any luck?

I get it. But that's what we did, and we've been good since. Plus the kernel change of course.

Checkout https://forum.proxmox.com/threads/vm-doesnt-start-proxmox-6-timeout-waiting-on-systemd.56218/post-276920

Did you follow all the suggestions earlier in this thread? I haven't had any issues since I reported things were fixed a while back.

We have ZFS for proxmox OS, and then a separate volume for VMs. We're not using LVM, but rather just ZFS, which I believe simply supports thin provisioning (otherwise we would see the storage usage shrink when we "fstrim -a" when discard is set).

This was very helpful. Thank you!

Good to know. That said, is there a certain percentage of frag that I should monitor for, that way I don't have to find out when customers start complaining about performance issues?