Recent content by weppa

I tried contacting the linux-kernel-block maintainer but I did the unthinkable ; I sent him a short and polite email instead of subscribing to a mailing list full of experts. I'l leave it to someone else to try to have these people care about the issue. I tried. If anyone is bold enough ...

You are right to underline that I (and some of us) should spend time migrating from mdraid, I'll dig deeper into that. However, that bug is a bug in the linux kernel (not specific to mdraid, it affect plain disks , loopbacks, etc) , it's even not specific to proxmox (but I discovered the issue...

At this stage, it clearly seems to be a bug in the kernel and I find it sad that so few people complain, which indicates not many people are monitoring their hardware closely. I have not identified a way to communicate with kernel devs, I mean something from this century and not requiring to...

Is there a way to « Escalate « this to Kernel maintainers ?

Interesting !

This creates spikes that are well above munin defaults for sending emails. And these defaults are set by munin maintainers ? It's 0:3 by default (warning/email if above 3 seconds). It's like that since 20 years I believe... WARNINGs: Write IO Wait time is 6.83 (outside range [0:3]). What's...

If this ever gets to a kernel developer : this is super easy to replicate ; just add munin package on a vm or LXC, or even on the host itself. monitoring disk latency is default. pve devs say for -6 update submodules and patches to Ubuntu-7.0.0-28.28i2 - upstream stable changes from...

I'm back at -5 and the problem vanished . So basically the problem appeared in -6 (as per Galaxis) , is still there in -8, I was just a bit late in the game. If it's a new kernel feature and not the sign of the disks getting crazy, it sure must be discussed with iotop, and anyone monitoring...

@Galaxis you're not crazy ; https://forum.proxmox.com/threads/increased-latency-on-disks-since-9-2-6-and-associated-7-0-x-kernel.185498/ That is my own topic I created. It's basically unusable (I've got 440 emil alerts this morning) and very concerning as this showed up on a variety of proxmox...

Thanks @Neobin ! In the meantime proxmox-boot-tool kernel pin 7.0.14-5-pve proxmox-boot-tool refresh UPDATE : I can confirm the problem DISAPPEARS with kernel 7.0.14-5 So it's specific to kernels after this one.

I have a couple of proxmox VE hosts, running 9.2.4 with 7.0 kernel. These systems are updated regularly (like once a month) with proper reboot For the last update (9.2.4 to 9.2.6 - on the 7.0 kernel) I have something weird happening that trigger alerts in MUNIN (yes i'm using munin) The...

Hello everyone, I've read and chatgpt'ed about this topic but I couldn't find the solution ; I need to upload 400GB+ from my home line (1/2MBps upload speed) to my PBS, in other words I need to make a 5 days upload (I'm backing up my NAS) There seems to be no "resume" capability in the PBC...

It seems to be a bug in the package rsyslogd 's apparmor config, inside ubuntu. It's been filed and corrected in september 2025 but, to date, the package hasn't been deployed to ubuntu 24 I don't really understand how this turns out to be a "PVE problem" once we run ubuntu in an LXC but as I...

Hi, sorry I'm not really into apparmor but apparmor is a kernel feature, and on an LXC ("inside the container") tuning the apparmor config files should have no effect ? Did you mean tuning the hosts' (the pve) config file ? Or do I simply need more experience to fully understand, in which case...

thanks to @jf2021 as well, sorry mate, you clearly deserve it more as you opened this topic in the first place :)