Search results

ok looks like i found solution :) https://forum.proxmox.com/threads/fstrim-doesnt-work-in-containers-any-os-workarounds.54421/ Can be closed

I use Ubuntu LXC CT on SSD lvm-thin storage and lvm-thin storage just keeps growing (about 90% full) but in LXC only 10% are used. Looks like its same problem like in this case https://forum.proxmox.com/threads/lxc-lvm-thin-discard-fstrim.34393/ But that script is not working Any help how to...

Sadly on my Topton SFF PC with Intel N6005 VMs wont boot on 6.1 kernel (same problems on unofficial 6.0-edge kernels). On 5.19 no problem. VMs are not able to boot from local-lvm storage (nvme-ssd). Its possible to create new VM run installation until vhdd partitioning, but then it fails. i get...

for ZFS you need also special vdev. So you need SSDs also for ZFS, otherwise performance will be even worst than now .

Update: backups starts working after many restarts od PBS server. So now i am lost :D

Any idea how to restart pbs connector on PVE ? I tried reload network interfaces and remove an add PBS storage in PVE but nothing helps. Only reboot

try xfs if you are using ext4. That helps me using PBS with HDDs.

Also is there any documentation about PBS architecture or i need to go on source code level ?

Every time after restart of PBS server, backups just stop working a we need to reboot all PVE nodes. INFO: starting new backup job: vzdump 131 --notes-template '{{guestname}}' --storage backup01-cl01-thiss --remove 0 --mode snapshot --node pve008 INFO: Starting Backup of VM 131 (qemu) INFO...

Ok looks like restart of the pve node fix this. But its possible to fix this without restarting pve nodes ?

Hi After upgrade to PBS 2.2 all backups just fails In log i see ERROR: backup write data failed: command error: protocol canceled INFO: aborting backup job INFO: resuming VM again ERROR: Backup of VM 233 failed - backup write data failed: command error: protocol canceled Some VMs...

Hi I am experiencing network latency spikes on VMs when backup job is running on same Proxmox VE node (PVE 7.0 + PBS 2.0) sometimes up to 800ms. I tried isolate vHDD with second storage , disable RAM ballooning and test network with iperf3, but none of this options are causing problem. I...

Ok looks like thats old job when server has old name. New jobs with new hostname are ok.

I want rename PBS server. I changed name in /etc/hostname and /etc/hosts, but looks like there is other config or bug ? When i try look at longest tasks on dashboard i get Bad Request (400) parameter verification errors parameter 'node': no such node 'lp-th-dc-backup01' lp-th-dc-backup01 is...

Yup ... on all nodes. So file restore is not currently working on actual version proxmox-backup-file-restore: 2.0.5-2. Maybe problem in this two commits ? - https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=d9822cd3cb30494b2fdabd7a3670e940ad8199ae -...

So looks like there is problem in 2.0.5-2 version proxmox-file-restore failed: Error: starting VM timed out (500) after downgrade to 2.0.4.-1 file restore is working again... (not for LVM with dash of course)

Ok so after update to latest packages from no subscription repo. proxmox-file-restore failed: Error: starting VM timed out (500) proxmox-backup-client: 2.0.5-2 proxmox-backup-file-restore: 2.0.5-2

Yes, file restore from LVM is working. But i think there is a bug with dash in VG name ? When VG name contains dash character, LV fails to mount.

We have same NICs Qlogic 57810S in 9 nodes and 2 nodes with Intel 4P X710-k. So then every port on one interface (4 virtual ports) are connected to one 10Gbit port on MXL, every virtual interface has same vlan configuration from switch. I asume there is no support for bonding like LACP in NPAR...

We use Jumbo frames. but for us there no way to use separate fyz. NICs for iSCSI. Servers are in blade chassi (Dell m1000e) so we have only 2x10Gbit to each server (switch in m1000e is 2x Dell MXL in switch stack configuration). So thats why we are using LACP bond. So iSCSI have dedicated vlan 2...