TrueNAS 12.0-U1.1

  4 minute read

TrueNAS Quality Lifecycle

Release StageCompleted QA CyclesTypical Use-caseDescription
NIGHTLY0DevelopersIncomplete
ALPHA1TestersNot much field testing
BETA2EnthusiastsMajor Feature Complete, but expect some bugs
RC3Home UsersSuitable for non-critical deployments
RELEASE4General UseSuitable for less complex deployments
U15Business UseSuitable for more complex deployments
U2+6+Mission CriticalSuitable for critical uptime deployments

January 15, 2021

iXsystems is pleased to announce the general availability of TrueNAS 12.0-U1.1! This is a minor version release to work around a critical ZFS issue that could impact systems with a rare but serious issue with data integrity under some very uncommon access patterns. To date iXsystems has only observed these issues while running with some very specific virtualization workloads, however ALL TrueNAS 12.0 or higher users are encouraged to upgrade their systems immediately to 12.0-U1.1 out of an overabundance of caution.

TrueNAS Enterprise customers with 12.0 installed can always contact iXsystems Support for assistance upgrading their TrueNAS deployments.

TrueNAS 12.0-U1.1 Changelog

  • NAS-108627 : While the underlying ZFS issue causing the instability is being resolved, there has been a temporary reversion of the ZFS CFA patch. This means that Asynchronous Copy-on-Write is temporarily disabled in TrueNAS 12.0-U1.1, with the goal to re-enable this functionality in a later TrueNAS 12.0 update release after this issue has been fully resolved.

Known Issues

KeySummaryWorkaround
NAS-107151Replication fails between legacy TrueNAS 9.10 systems and 12.0-BETA1 systems.Due to numerous improvements in the replication engine and ZFS, FreeNAS/TrueNAS 9.10 systems (or earlier) can no longer replicate to or from TrueNAS 12.0. Update the legacy TrueNAS system to FreeNAS/TrueNAS 11.3 or newer.
NAS-106992Persistent L2ARC is disabled by default.While the underlying issues have been fixed, this setting continues to be disabled by default for additional performance investigation. To manually reactivate persistent L2ARC, log in to the TrueNAS Web Interface, go to System > Tunables, and add a new tunable with these values:
  • Type = sysctl
  • Variable = vfs.zfs.l2arc.rebuild_enabled
  • Value = 1
TrueNAS "root" user account cannot be an SMB user.This is an intentional change to improve software security and suitability for deployment in a variety of environments. Update the SMB configuration to use a different user account.
NAS-108580U1 update is incorrectly flagged as "Not a Production Release"This warning is a result of the Enterprise train not being activated yet and can be safely ignored. This will be automatically corrected on February 2nd, 2021 when the Enterprise update train is activated.
Performance regressions on some Intel and Chelsio Cards vs 11.X SeriesOur team is aware of some performance regressions when using Intel and Chelsio Network Devices on TrueNAS 12.0. These issues have been identified in upstream FreeBSD 12.2 and fixes are now pending to resolve these regressions. An update release will be issued in the near future.
Due to continuing improvements in the upstream samba project, some operations available for auditing have changed names between the 11.3 and 12.0 releases. For more information, see this commit for the expanded lookup table. Users who have configured this module have done so via auxiliary parameters. These parameters must be adjusted to use the new names for the VFS operations.List of impacted operations with old and new names are as follows:
  • rename = renameat
  • unlink = unlinkat
  • mknod = mknodat
  • link = linkat
  • symlink = symlinkat
  • readlink = readlinkat
  • mkdir = mkdirat
NAS-109066Switch middleware rsync plugin to "new compression"Due to security vulnerabilities in zlib, built into rsync in the version included in TrueNAS and broken NFSv4 ACL support in rsync in upstream FreeBSD port, we switched to building rsync against the base zlib in freebsd. Per rsync man page:
  • Note that if your version of rsync was compiled with an external zlib (instead of the zlib that comes packaged with rsync) then it will not support the old-style compression, only the new-style (repeated-option) compression. In the future this new-style compression will likely become the default. The client rsync requests new-style compression on the server via the --new-compress option, so if you see that option rejected it means that the server is not new enough to support -zz. Rsync also accepts the --old-compress option for a future time when new-style compression becomes the default.