proc_stat_read: Write to cache was truncated

[Laurent37100]

Hello,

After upgrading from proxmox v7.3 to 7.4 syslog is flooded by this error message happening 1 or 3 time(s) by second. Any idea ?

Apr 17 09:43:27 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:27 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:28 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:28 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:29 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:29 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:30 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:30 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:31 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:31 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:32 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:32 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:33 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:33 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:34 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:34 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:35 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:35 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:36 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:36 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:37 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:37 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:38 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:38 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:39 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:39 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:40 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated
Apr 17 09:43:40 xx lxcfs[3329]: ../src/proc_fuse.c: 986: proc_stat_read: Write to cache was truncated

 

[Moayad]

Hi,

Did you reboot the Proxmox VE after you update it?

 

[Laurent37100]

Yes everything up-to-date and server rebooted.

 

[Laurent37100]

Is this coming from a container ? How to identify the container sending error ?
I'm running some container running as privileged one, any link with this issue ?

 

[Moayad]

Hi,

I can see like the above issue in our forum below link [0]

[0] https://forum.proxmox.com/threads/cannot-open-proc-stat-transport-endpoint-is-not-connected.111312/

 

[Laurent37100]

None of the fixes provided are working

 

[deniax]

i have the same problem.
All my containers are privileged and restarting Proxmox gives the same error

I do need to say I am running proxmox-ve: 7.4-1 (running kernel: 6.2.9-1-pve)

Full list:

Spoiler: Package Versions

proxmox-ve: 7.4-1 (running kernel: 6.2.9-1-pve) pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a) pve-kernel-6.2: 7.4-1 pve-kernel-5.15: 7.4-1 pve-kernel-6.2.9-1-pve: 6.2.9-1 pve-kernel-6.2.6-1-pve: 6.2.6-1 pve-kernel-5.15.104-1-pve: 5.15.104-2 pve-kernel-5.15.102-1-pve: 5.15.102-1 pve-kernel-5.15.74-1-pve: 5.15.74-1 ceph-fuse: 15.2.17-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve2 libproxmox-acme-perl: 1.4.4 libproxmox-backup-qemu0: 1.3.1-1 libproxmox-rs-perl: 0.2.1 libpve-access-control: 7.4-2 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.3-4 libpve-guest-common-perl: 4.2-4 libpve-http-server-perl: 4.2-3 libpve-rs-perl: 0.7.5 libpve-storage-perl: 7.4-2 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.2-2 lxcfs: 5.0.3-pve1 novnc-pve: 1.4.0-1 proxmox-backup-client: 2.4.1-1 proxmox-backup-file-restore: 2.4.1-1 proxmox-kernel-helper: 7.4-1 proxmox-mail-forward: 0.1.1-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.6.5 pve-cluster: 7.3-3 pve-container: 4.4-3 pve-docs: 7.4-2 pve-edk2-firmware: 3.20230228-2 pve-firewall: 4.3-1 pve-firmware: 3.6-4 pve-ha-manager: 3.6.0 pve-i18n: 2.12-1 pve-qemu-kvm: 7.2.0-8 pve-xtermjs: 4.16.0-1 qemu-server: 7.4-3 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.8.0~bpo11+3 vncterm: 1.7-1 zfsutils-linux: 2.1.9-pve1

 

[Laurent37100]

Same here; but with 5.15 kernel, so I imagine this as nothing to do with kern release. I must add that I'm running on a ZFS FS.

# pveversion --verbose
proxmox-ve: 7.4-1 (running kernel: 5.15.104-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
pve-zsync: 2.2.3
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1

 

[Laurent37100]

while waiting for a fix the real question is "can this error may corrupt data?" if anyone have an answer please share

 

[DemiNe0]

while waiting for a fix the real question is "can this error may corrupt data?" if anyone have an answer please share

It's certainly possible.