Number of clicks required to download the ISO from website keeps going up. Currently at 5. Also it takes a while to figure out what it is that you guys make, because it goes from Get TrueNAS to Get TrueNAS Community edition and then to Get TrueNAS Scale. It seems like it’s somehow a problem for you guys to just give me an iso link.
SCALE UI traditionally broken, i.e. creating a ZVOL with size larger than 80% of available dataset space (or whatever is set as threshold) results in error, clicking “Force size” doesn’t unblock the Create button, so I have to change some other field and change that back to refresh the form validator. Things like that are broken since forever.
SPICE is without change since forever also, doesn’t work. I can’t get Ubuntu 24.04.1 to actually start up. Spice keeps glitching out, it’s logs start with some permission denied message.
UI being unhelpful as always here - “Web Interface” checkbox does nothing, spice still works even if unchecked before VM start, TightVNC can’t connect.
Absolutely horrendous POSIX ACL with nondescriptive errors which somehow keeps getting worse from version to version.
I migrated to Scale in 7/2022 after everyone said it’s ready, it wasn’t. Now I tried setting up Scale in my new office once again, it feels like the quality of the CE just keeps degrading. I see redesigned UI (unhelpful). Dashboard gives me red and orange warnings on a dataset, because it’s 90% full, despite having 95% warning and alarm thresholds, etc.
I’d be worried to call this a beta version, tbh. I just wasted like 6 hours trying to set this thing up, I’m in the process of wiping everything and installing CORE in hopes you didn’t break anything in any of the updates.
Additionally, the “truenas_admin” mandatory username for admin user is also a stroke of genius, thanks again for this unwanted and pointless change that’s going to annoy people everywhere.
The backend and error messages haven’t really changed since angelfish (22.02). The requirements for a valid POSIX1E ACL themselves haven’t changed really since they were implemented.
Once an API has been defined there’s generally little reason to change it. For example, the general APIs for getting / setting ACLs haven’t changed since TrueNAS 12 IIRC.
The change from admin -> truenas_admin was necessitated for compatibility in some environments that have an admin user defined via LDAP. Name collisions are bad. This should only impact new installs.
Definitely the first time since I’m seeing an error about needing a “mask” to give a user inheritable permissions. That entire ACL manager is cancer, always has been. Switching to NFSv4 permission model gives apocalyptic warning message with vague description that says you kinda sorta have to do this huge and complex permission migration thing manually otherwise it’s gonna randomly break the permission model (no link, how to or manual included, good luck).
Just seriously sometimes I wonder where is TrueNAS getting all this praise from. This is genuinely terrible product to use, because almost every piece of it is broken in some way and has been forever.
Definitely the first time since I’m seeing an error about needing a “mask” to give a user inheritable permissions.
Not really. I checked. The requirement for defining a mask has been present since 22.02. The UI for this could be improved to help users form valid ACLs, but specifying a mask entry has always been required. It defines the maximum permissions granted to supplemental entries (part of the POSIX1E spec).
Switching to NFSv4 permission model gives apocalyptic warning message with vague description that says you kinda sorta have to do this huge and complex permission migration thing manually otherwise it’s gonna randomly break the permission model (no link, how to or manual included, good luck).
There is not migration between POSIX1E and NFS4 acltype (they are stored on-disk separately). This means you have to redo your permissions on the dataset from scratch after the change (i.e. recursively set new ACL). This has do with how the information is stored on disk and there’s no way to paper it over.
