LVM full space

[frankz]

Hello everyone I suddenly find myself with the root disk full and I can't figure out what it's busy with. Can someone tell me what to do?


I also noticed that the log files were 90 GB

ug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 15 17:43:40 pve4 kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4

Virtually the messages and kernel.log files have become huge due to these continuous writings. It seems to be an AER-related issue that seems to be disabled at boot time. How can I do it?

 

[bbgeek17]

start with trimming the log "echo "" > logfile"
continue with finding files that take a lot of space : du -h -d1 -x /
its possible that the log file is the culprit, the kernel is clearly upset with some device (try lspci -vvv).
reboot, after trimming the log, to see if it resolves.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[frankz]

start with trimming the log "echo "" > logfile"
continue with finding files that take a lot of space : du -h -d1 -x /
its possible that the log file is the culprit, the kernel is clearly upset with some device (try lspci -vvv).
reboot, after trimming the log, to see if it resolves.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Yes, I think the problem is related to AER, but I have recently encountered this error since I made the updates.
I also read in a post someone who had the same problem but not on proxmox and indicates to do this:

If this doesn’t work, you may get rid of kernel messages with pci=noaer, but this wouldn’t fix the errors (these are reported as corrected, though), but only disable errors reporting so that it doesn’t spend time filling your kernel log files.

 

[frankz]

start with trimming the log "echo "" > logfile"
continue with finding files that take a lot of space : du -h -d1 -x /
its possible that the log file is the culprit, the kernel is clearly upset with some device (try lspci -vvv).
reboot, after trimming the log, to see if it resolves.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

At the moment I added in the grub the parameter

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=noaer"

Looking at the logs I no longer see the correction error. But will I have done a correct operation or not?

What do you think?

 

[bbgeek17]

I dont know. As long as everything is working to your satisfaction, you should be good.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[frankz]

I dont know. As long as everything is working to your satisfaction, you should be good.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

No, it's not about satisfaction, but understanding what's been done. Reading a small docs, it seems that the AERE parameter is linked to another MSI parameter, which may not work or rather not be compatible with some hardware cards. However, thank you very much for intervening.