Search results

One of my PBS datastores are showing the following error across multiple nodes proxmox-backup-client failed: Error: EUCLEAN: Structure needs cleaning (500) What could be the cause of this? The datastore verify job passes

Which part? So I can google and hopefully find some tests to run.

Yes a lot of errors but not exactly sure when it began https://pastebin.com/BUg1mCTL

I am getting the following error code for all virtual machines. Rebooting the PBS node temporarily fixes this. VM 231 qmp command 'backup' failed - backup connect failed: command error: unable to read "/mnt/storage2/PBS/Alpha/vm/231/owner" - Input/output error (os error 5) What are some of the...

Any ideas why this cron doesn't work? 30 * * * * /bin/echo | pvesm list PBS

Ok thanks makes sense. Backups are daily yes. How can I update this metadata then? I would like to do it at certain time daily with a cronjob on the PBS server.

I am not sure if we are on the same page. Every day when I load the PBS for the first time that day it loads extremely slow https://gyazo.com/3784ccd0416d5d300da6f69f0029e181 leaving it a few minutes once I come back it starts loading fast as if the layout of the PBS data gets cached (like a...

Just tested this happens when the load is quite low too. Is there some sort of cache that gets updated on requests? I have found once one server loads the backup list they all do fast afterwards even if not in the same cluster.

No one had this issue?

But wont that stop working once you move the VM to another node without making any changes?

As you can see from this gif https://gyazo.com/3f5c7ff162709258e8f335aa0bc1d728 PBS sometimes takes 30+ seconds to load and even timeouts. How can I diagnose the issue? The latency between the servers is low. It feels like once it loads other backups of other virtual machines load faster as if...

Today after months of this configuration working it has just stopped. When trying to restart the network I get the following error warning: error while writing to file /sys/class/net/eth3/mtu: [Errno 19] No such device /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface...

I just set up another node and it worked fine now. The only thing I did different was installed console-setup (apt install console-setup) and afterwards ran update-grub update-initramfs -u -k all Maybe you can try do that in chroot Can't remember exactly what I done in but I went into BIOS...

This seems to happen daily at 6:30-7AM. Nothing I know of runs then. I do have daily PBS but that runs much earlier.

That's an option but not really ideal.

I had this problem with an OVH server. Luckily it has IPMI access so I changed the boot order to skip the issue I had https://forum.proxmox.com/threads/grub_is_lockdown-after-upgrade-to-7.96819/ Someone else told me they done the following via rescue mode "I booted in rescue @ ovh, reinstalled...

Nothing? This must be a key feature in some production environments.

Can someone please explain to me why the CPU limit seems to sometimes only work for a few hours? Also is there any alternative ways on limiting CPU. In production environments where you are selling CPU (fair share) resources how else can I limit CPU abusers

Any suggestion on a fix for this? I have tried adding net.ipv4.conf.vmbr0.arp_ignore=1 net.ipv4.conf.vmbr0.arp_announce=2 To flush ARP cache I run the following which temporarily fixes ip -s -s neigh flush all

Understand the risks I need the extra disk space and possible performance. I will try running a repair first or try telling btrfs to ignore checksum errors. From looking around writeback or writethrough cache on COW filesystems is required. Direct i/o isn't supported on btrfs with files that...