I’m a bit surprised there isn’t a public forum for bugs or issues for nightlies that people could just look at and know they aren’t going crazy or even to confirm similar findings or say I’ve posted a trouble ticket for this or that issue.
Updated from 26.0.0-MASTER-20260901-020200 to 26.0.0-MASTER-20260930-020149 and found NVMe-oF/TCP broke on Linux. You get write access to the mounted drive for seconds to a minute before it reverts to read only. Creating a new zvol will allow you to mount but not format/write to the disk. You can remount the drive to write to it again only to have it revert to read only. Reverting back to 26.0.0-MASTER-20260901 fixes the issue.
Ticket submitted - Jira
Some software development will fork the current branch, (even before it’s general availability release), to start working on the next release. Then back port any bug fixes or added features to both branches.
However, you are probably right. With your Current version of 27.0.0.xxx already being the next development branch, the Update version is not likely for the year 2028.
However, as long as they don’t bring back the Release That Shall Not Be Named, I guess it’s okay.
This does remind me that when they decided to come out with a Linux variant, I told them that it both be a lot of work to keep the kernel current. And it would be too much work to release twice a year. Yet, people in the Linux world expect their shinny new wiz band do hicky to be supported immediately, perfectly without any effort on their part.
This change to once a year major release is going to make people using brand new hardware that only has latest kernel support, unhappy. But, what else is new.
download.truenas.com only has TrueNAS-26-BETA, TrueNAS-26-Nightlies, and TrueNAS-27-Nightlies right now. There is no TrueNAS-28 directory there, so the 28 ISO nightlies dont look published yet.
28.0.0-MASTER-20261009-230212 still has the NVMe-oF/TCP write issues to read only for the mount in Linux. Not sure if it’s related to configuration of the svdev on the pool. Reverting to 26.0.0-MASTER-20260901-020200 resolves the issue.
Did some due diligence for the NVMe-oF/TCP write issue. In Nightly versions 26.0.0-MASTER-20260901-020200 or older, I didn’t have the issue with my configuration mounts for the NVMe-oF drive in Ubuntu 26.04.1 LTS.
Recently tested with 28.0.0-MASTER-20261011-230237 & TrueNAS-27.0.0-MASTER+20261012-020146 for SMB3 & NFS4 shares whilte testing NVMe-oF/TCP zvol and noticed the issue would only happen when writing files using Steam client and not from file manager or terminal using fio.
Fix, disable journaling for NVMe block device using ext4 format.
Edit /etc/fstab
UUID=“uid of nvme mount” “dir of mount” ext4 defaults,nofail,_netdev 0 2
sudo tune2fs -O ^has_journal /dev/“nvme device”
NVMe-oF/TCP mounts now work as expected.
Tested Ubuntu 26.04.1 LTS
Proxmox Server 9.2.21
