The TrueNAS team is pleased to release TrueNAS 25.04.2.4!
This is a small maintenance release that includes fixes for ACL editor behavior and SMB thread stability.
Notable Changes
Fixes an issue where the ACL editor ignored unchecked “Apply Owner” and “Apply Group” checkboxes and always applied owner/group changes recursively, potentially causing unintended ownership changes (NAS-137378).
Fixes an issue where SMB threads could become stuck at 100% CPU usage on Windows clients, causing Windows Explorer to become unresponsive until the thread was manually killed (NAS-137095).
Thank you. The “Fixes an issue where SMB threads could become stuck at 100% CPU usage on Windows clients, causing Windows Explorer to become unresponsive until the thread was manually killed” sounds critical to me, thus patching now.
is it my imagination or does smb for windows 11 clients have issues?
I recently changed my cpu, motherboard and ram from AM4 to a new AM5, but they still face the issue where uploading from desktop to truenas is slower than uploading from truenas to desktop in local using SMB explorer.
So i get roughly 500-600 Mb/s one way, but only 300-400 Mb/s the other way.
Has anyone else experienced this? this does not seem to be a truenas specific issue, cause last time i tested with a QNAP i got similar results, making me think it’s something windows 11 related.
as a layman just wondering if this smb fix has any relation to that? or something.
All i could find was this
supposedly it was fixed but my results i’m doubtful
So I was on 24.10.2.2 and just upgraded to 25.04.2.4 about 30 mins ago. I want to give a big Thank You! to the TrueNAS team. The upgrade was smooth and fast. NO ISSUES. I waited specifically so my virtual machines would have smooth upgrade path (I know I could have upgraded a little bit earlier). Great job guys!!
But my domain connection failed… had to roll back to 25.04.2.1 and completely leave and reset the domain (its very finicky about acutally deleting the domain account and krb5.keytab). I had a healthy domain connection for about a month before attempting to upgrade.
Got “KEYRING:persistent:0: Credentials cache does not exist” at one point also. Seems to be far too easy to get the domain connection into a broken state and hard to get it out of it.
Isn’t that still rather long in the (fang)tooth mouth for a shorthand?
Anyway, Goldeneye being the 007th major version of SCALE/CE, will bring a new twist to naming, I presume…
(Yes, I know it’s “Goldeye”. Good luck with that!)
