Cesar Talledo

> Yes, I run findmnt with watch -n 1 "findmnt | grep virtual" while (crub_all) is sending infinite umount calls but nothing much is showing up in the findmnt. Should...

If that doesn't work, maybe the unmount is happening in a dedicated mount namespace. In that case, from inside the sysbox container, find the PID of the `crub_all` process that...

Hi @sibidharan, Thanks for the extra info. > Disabling these services are enough or this has to be fixed in Sysbox also? Since we are having trouble understanding the issue...

Hi @bushev, > The CPU is still at 100% usage due to Sysbox FS Mmm ... strange. Must be the workload inside the sysbox container triggering the problem. Is there...

Hi @Kl0ven, thanks for reporting. Yes I am able to reproduce with the `nestybox/ubuntu-noble-systemd` image. There must be something in that image that is causing high CPU usage, I'll investigate....

For the `nestybox/ubuntu-noble-systemd` image, I confirmed that it's the `e2scrub_reap.service` that is causing the high-CPU usage inside the Sysbox container. I need to understand what that service is doing and...

I opted for a quick solution of disabling the `e2scrub_reap.service` in the `nestybox/ubuntu-noble-systemd` image. The rationale is here: https://github.com/nestybox/dockerfiles/pull/38 I've pushed the new image already to Dockerhub, so you should...

Hi @sibidharan, Thanks; yes, we should disable that `e2scrub_all.timer`; I'll do that in the `nestybox/ubuntu-noble-systemd` image (and derivatives of it).

Hi @bushev, Thank you very much for reporting the problem you are having. I was able to easily reproduce with your instructions, thanks. On a quick look, it seems like...

> I think it's a bug in sysbox-fs, but one that we have to think carefully how to resolve. Potential fix here: https://github.com/nestybox/sysbox-fs/pull/98