You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the last 3 months, every day or so a complete machine lockup. Nothing obvious in kernel logs, but just caught 'zed' locking the machine. Load averages rises by about 1 per second, all cores go 100% until machine locks. Memory only slightly increased with lots free. Saw 10-12 z_* threads running just before zed went 100%.
Describe how to reproduce the problem
At random during normal system use when problem occurs, nothing to disk/cpu heavy (e.g. web browsing).
Include any warning/errors/back-traces from the system logs
Nothing found in the logs, only caught issue as 'top' was open.
The text was updated successfully, but these errors were encountered:
I remember it was when kernel 6.10 came out (July '24), as I assumed it was a kernel issue. 6.10 had the issue, but 6.9 didn't. Annoyingly, I upgraded to FC41 and no longer had 6.9 available - and the problem came back.
I upgrade ZFS as it become available on fedora updates (which is usually a couple of days after release), so I guess I was running 2.2.4 when the problem first appeared.
I've been chasing it as a kernel issue, but now having caught zed it's maybe a kernel-zfs interaction issue?
System information
Describe the problem you're observing
For the last 3 months, every day or so a complete machine lockup. Nothing obvious in kernel logs, but just caught 'zed' locking the machine. Load averages rises by about 1 per second, all cores go 100% until machine locks. Memory only slightly increased with lots free. Saw 10-12 z_* threads running just before zed went 100%.
Describe how to reproduce the problem
At random during normal system use when problem occurs, nothing to disk/cpu heavy (e.g. web browsing).
Include any warning/errors/back-traces from the system logs
Nothing found in the logs, only caught issue as 'top' was open.
The text was updated successfully, but these errors were encountered: