billbord

I'm less-than-thrilled to report the issue is back in 6.9.2.

I'm thrilled to report that 6.9.1 fixed this issue for me.

I'm still seeing this, I hate it so much.

I have the exact same behavior, my disks spam these notifications (and "utilization back under threshold" notifications) all day every day. I've set each threshold to 0 (off) but it didn't help.

Is there a way to kill the mylar process and re-run with the -v flag from within the container's console? I'm trying to pull the verbose logs to troubleshoot a DB problem with the developer. I can't seem to get a "kill" to stick within the console so far. I'd really rather not create an entirely new image - it's beyond my skills. Thanks in advance. Edit: I never did figure out how to kill the process - the s6-supervisor gets in the way I think. I was able to copy the run file to my cache drive, make the edit, then copy it back successfully and have the verbose logging now (in case anyone else ever runs into this). I imagine that'll go away the next time the container is updated, but it's persistent through container restarts for now.