Search results

Unfortunately Snapshots are not remote and they prevent migrations between nodes. (local storage) I do think a good common ground would be to have an option to set a lower value than 24hours. (6hours, 12hours, etc) If atime is broken, surely relatime will also be broken ? From my estimation In...

For us using PBS offers us an option to make fast, low impact backups with high frequency on a multitude of datasets. With Rapidly changing data on web, database, email, file servers, why would we want a daily backup only which will be many many hours old, when we can have X 15min backups and X...

We run GC and prune tasks every 30mins, backups from a cluster are done every 15mins. But we land up with pending removals of around 10TB per 24hours. atime is enabled (relatime disabled), Is there any way to force GC to remove after 4 or 6 or 12hours and not wait 24hours and 5mins ?

^^ has the potential to kill all the backups, as some chunks are now marked "old", when they are actually needed and should have current access times

has any progress been made towards this ? It is pretty easy to saturate a 20Gbit link with backups from a cluster and the only solution is to limit the number of concurrent nodes.

We are saturating a 20Gbit link with backups from the cluster and on large clusters one needs to be able limit the number of concurrent nodes which run backup tasks.

has any progress been made towards this ? We are saturating a 20Gbit link with backups from the cluster and need to limit the number of concurrent nodes.

Did you ever find the root cause and a fix for the problem ?

Did you ever find the cause for the above or a solution ?

Same issue with one of my nodes

+1 fall back to acpi when quemu-guest-agent fails to shutdown / restart the server

+1 same issue, hopefully this gets added to a future update

@wolfgang hardware is fine, the kernel is tainted and failing. Any advice would be appreciated.

screenshot of terminal

Starting a VM or a container which uses ZFS for storage results in a kernel panic. There were no errors or issues before upgrading to the latest kernel. Any suggestions ? AMD EPYC 24core, 3x1.92TB SSD in zraid1, 2x200gb SSD for boot/os Message from syslogd@prx-ax at Aug 29 06:37:58 ...

The random EYPC crashing bug fix has been added to install-post.sh @ https://github.com/extremeshok/xshok-proxmox

Script was renamed to install-post.sh

The unit file detects the presence of "/usr/sbin/ntpd" if this is found, the service will never enable/start Use the following commands apt purge ntp systemctl daemon-reload --- I have updated the post-install.sh script located here https://github.com/extremeshok/xshok-proxmox

Tested on a dual 24core (48core, 96thread) AMD EYPC, working perfectly in production. 4.15 is a must have on AMD EPYC. My Post Install Script (postinstall.sh) located at https://github.com/extremeshok/xshok-proxmox/ will automatically Detect an AMD EPYC CPU and install the kernel 4.15.

Thanks for the heads up, I have added this to the Post Install Script (postinstall.sh) located at https://github.com/extremeshok/xshok-proxmox Which adds the 'reboot-quick' command