Recent content by christian.g

As @fabian suggested, you should use tmux or screen in your ssh session. In case you get disconnected, the dpkg process will continue und you can re-attach to the running tmux/screen session after re-connecting through ssh. 1. ssh into your node 2. start tmux 3. run you dpkg command if you...

Thanks for the info. Right now i'm having a hard time fighting a few heavy problems with PVE 9. All VMs on node1 lost network connectivity and i had to reboot the node. After it came back and VMs started migrating back the next problems showed up on a another node (see below) Two different...

Hello, the dropdown to select a network for Migration/Replication doesn't show/select the networks but the IP for the node one is logged in. Example on node 1. All networks are X.X.X.0/24 And configured IPs are X.X.X.1/24 Selecting one of those entries sets the IP (ex. 10.0.110.1/24)...

Thx for opening a Bugreport. Well yes, VMs may need a different amount of time to migrate. That's completely legit. Consider an Application Server and a corresponding Database Server VM. You want them on the same node. The Database Server VM may take even minutes longer to migrate (RAM is...

Hello, we've upgraded our cluster from 8 to 9 and created a few resource affinity rules (no node affinity rules present). For example there is one positive affinity rule for VMs 910 and 911. Both are simple Linux VMs with backing ceph storage (ssd pool). No PCI devices or anything else is...

For testing I added a special device (mirror of 2 256GB NVMe) to the pool on PBS site and did set the small files limit to 32k on the dataset. It helped a bit. I did get an overall backup speed of 100MiB/s. I will leave it added for now until a better solution is available. Warning: A special...

A Special Device is not a write cache but a "normal" vdev. Meaning, the data stays there and doesn't get flushed to the spinning disks. We need more something like bcache in front of the zfs pool but this introduces a complex setup and i personally think it would make way more sense to implement...

Not sure what you mean. ZFS doesn't have a Write Cache. SLOG is not a Write Cache.

Thanks but I suspect this will slow down backups and sounds more like a workaround. Why not implement a SSD/NVMe Write-Cache in PBS? Add a zpool of mirrored fast devices with enough capacity, write there then flush to spinning disks in background. That way one can have fast and save backups...

Any update on this? We have this problem on a regular basis and it's becoming a real show stopper.

All of your points are valid but in the end the Cluster has to be fast enough to fit the needs and with Cache "None" it's not. I generally favor safety over performance but in this case the numbers are far to bad and users have to do their work without going to have a coffee until the...

True but i would appreciate if instead of just saying "Not true" you would provide usable information. :) I wrongly interpreted the Discard Option! It is about thin provisioning and not about flash storage. "Disk images in Proxmox are sparse regardless of the image type, meaning the disk image...

Sure, that's what writeback does. :) Ok, so the usual writeback drawbacks. Thanks. Yes, but this only applies to flash storage. I just wanted to point out that discard impacts performance. In my case i need discard but this does not automatically applies to others. I've tested on flash...

Till now a few suggestion have been provided by the community like - manually increase the memory buffer size - add a fast and large enough buffering device like a PCI NVMe or a ZFS mirror of them - use storage snapshots if available (ZFS/CEPH) - use backup fleecing Is Proxmox working on any...

I know this is an old thread but i'm currently investigating IOPs on our Ceph cluster. Test VM Debian 10 (Kernel 4.19) Test Suite fio with 4k randrw test Every test was repeated 3 times First tests to raw rdb block devices from within the VM to identify the best BUS (SCSI vs Virtio) with no...