Search results

Hi all, I'm having the same exact problem on a production environment. Last year we had to replace the system NVMe due to SMART error, now we're in the same situation and were investigating. Here are the statistics: The weird 661TB written in 6937 hours (~290 days) is completely crazy. At...

Maybe I solved the issue, based on this thread. I stopped proxmox-backup-proxy service, then moved the entire /var/log/proxmox-backup folder to an HDD partition, then soft-linked the new folder to the original path: systemctl stop proxmox-backup-proxy mv /var/log/proxmox-backup/...

I already tried the iotop way: tons of proxmox-backup-proxy lines, high current disk write, but no clue on what (or at least, no clue to me): What is strange is the really weird amount of disk usage: we're talking of 661TB of data written on a 256GB SSD in ~300 days of usage... Tomorrow I...

Hi Dunuin and thanks for your reply. I tried your suggestion, setting in the journald.conf file the Storage=volatile variable, restarted the systemd-journald service and now the logs are written on RAM in /run/log/journal. Unfortunately, the problem seems not resloved at all: despite the change...

Hi all, I'm using a Proxmox Backup Server instance as a backup pool of a PVE cluster. Despite the PBS pool is mounted on a RAID5 4x16TB HDD, and the 256 nvme has only OS on it, it seems the nvme keeps doing a very very huge traffic (645TB over less than 1year period): the command iostat 1...