I have a secondary/testing system which was running 25.04-BETA.1 just fine.
It is an unsupported configuration, as the boot-pool and an “ssd” pool are on the same physical SSD, but it has worked just fine since TN Scale 22.xx.
But with RC.1, it froze up multiple times now. The first time, the web UI eventually became responsive again and this was logged before/during/after:
Notice the “task zvol_tq-1:341 blocked for more than 120 seconds()”. I wonder if that caused the “freezing up” issue? The “ssd” pool is running a Windows Server VM (idle), so I guess that’s the referenced zvol task.
Then again, today, I noticed that the power consumption was high (no scrub) and upon checking, the web UI and a remote desktop connection to the Windows VM were both unresponsive.
This was in the logs (probably more above that I missed to record, hopefully in the debug file though):
The machine runs an Intel E3-1231 v3 @ 3.40GHz, with 16 GB of ECC RAM and just the one Windows Server VM with 4 GiB reserved.
The ssd and boot-pool are on a Samsung SSD 860 EVO 500 GB SSD that’s still working correctly as far as I can see. Force-restarted the server now and it’s up again.
Is it worth to create an issue for this, even if the configuration with ssd/boot-pool on the same SSD is unsupported?
Again, it’s just a testing system—my main system is obviously not set up like that—but it’s still weird that it froze up multiple times with RC.1 now, when it never did before…
EDIT: The ssd pool had autotrim on. I don’t think this has been an issue in the past, but I’ve disabled it for now to test if that’s somehow related, as I think I read some OpenZFS issue at one point where issues with autotrim causing lockups were mentioned. A scheduled trim task was recommended instead there.