TrueNAS 13.0-U6 is Now Available

[anodos]

Unfortunately no smb related bug fixes ;-(

There were SMB-related bugfixes mentioned in the release notes. (xattr removal failure)

 

[Jailer]

Unfortunately no smb related bug fixes ;-(

I think SMB bugs are a feature.

 

[eturgeon]

Sry, but I was unable to find the relase notes;

13.0 Release Notes

Highlights and change log for the current major version of TrueNAS CORE.

www.truenas.com

or.

13.3 Version Notes

Highlights and change log for each TrueNAS CORE 13.3 release.

www.truenas.com

It is https://www.truenas.com/docs/core/13.0/gettingstarted/corereleasenotes/#130-u6
I fixed the link. Thanks for reporteing.

 

[Davvo]

Almost boring update, downloaded it yesterday and tried to apply today: got a https timeout error or something similar; refreshed the page, applied again, the download and installing process executed as expected. No apparent issues rn.

 

[joeschmuck]

Almost boring update

Boring is good to me. I'm not a fan of problems.

 

[awasb]

Installed without a single hickup on the test systems over here.

 

[morganL]

Unfortunately no smb related bug fixes ;-(

Major Samba updates will be in 13.1.... for any specific issue, identify the bug fix you need.

 

[Grid21]

I have a question, 1. How do I update, and why does it ask me to save Secret Keys, and 2. I noticed a link that reads "Before updating, please read the release notes." and then takes me to talking about "Nightly" build updates. So is this a dev update? Or a full stable update that's ready for production?

 

[Patrick M. Hausen]

1. It asks you to save your current configuration and if you want to save any secret keys with that.
2. Bug, the link to the release notes is wrong. See here.
3. Apart from that it's a stable supported release.

 

[Kevin Horton]

It is https://www.truenas.com/docs/core/13.0/gettingstarted/corereleasenotes/#130-u6
I fixed the link. Thanks for reporteing.

But, if I click the link for the release notes from the System / Update in the TrueNAS-13.0-U5.3 UI, the link takes me to a Nightly Version Notes page

 

[Palladio]

I updated my system today with this, and it went smoothly.

 

[Juan Manuel Palacios]

Does anyone know if the ZFS bundled in this new TrueNAS Core release is 2.2.0? Is it affected by this bug? https://github.com/openzfs/zfs/issues/15526 (which was worked around in 2.2.1, https://github.com/openzfs/zfs/pull/15529).

Thank you,

 

[winnielinnie]

It’s on 2.1.13.

 

[Juan Manuel Palacios]

It’s on 2.1.13.

Awesome, thank you for that info!

 

[winnielinnie]

Awesome, thank you for that info!

Man, that's a really nasty bug. Now I'm worried...

Apparently, it's been reproduced even with Open ZFS 2.1.13. So it doesn't only affect 2.2.0. Block-cloning, while not the cause of the problem itself, seems to trigger the conditions for the bug to more likely occur. (It still occurs in 2.1.13, which lacks block-cloning.)

The "fix" for 2.2.1 is simply to disable the Block-Reference Table by default. (It's more like a temporary safeguard until they can truly fix the bug.)

There's a lot of discussion going on in that bug report. (Still ongoing, as of an hour ago.) It makes me feel uneasy that using a stable version of ZFS can silently corrupt your data.

They believe it might be the way coreutils works with ZFS. Yet, it was reproduced on FreeBSD 14.

What the heck happened?

 

[Grid21]

Can anyone give instructions about updating and what to do when asked about saving secret keys? I want to do this update correctly and not lose anything.

 

[winnielinnie]

A "reproducer" script was created in the discussion by Tony Hunter.

https://gist.githubusercontent.com/tonyhutter/d69f305508ae3b7ff6e9263b22031a84/raw/c543f1c60eec6c115bd3d1d97fa45c4bb8b3e573/reproducer.sh

You can test it yourself in a temporary, junk folder. It's meant to be run in parallel (4 at once) to try to trigger the bug.

Here is his post for reference:

some copied files are corrupted (chunks replaced by zeros) · Issue #15526 · openzfs/zfs

System information Type Version/Name Distribution Name Gentoo Distribution Version (rolling) Kernel Version 6.5.11 Architecture amd64 OpenZFS Version 2.2.0 Reference https://bugs.gentoo.org/917224 ...

github.com

Apparently, someone was able to consistently reproduce the bug on TrueNAS Core 13.0-U5.3, ZFS 2.1.11.

I might spin this up myself. Tomorrow might not be feasible though.

This type of bug in ZFS really worries me.

 

[morganL]

A "reproducer" script was created in the discussion by Tony Hunter.

https://gist.githubusercontent.com/tonyhutter/d69f305508ae3b7ff6e9263b22031a84/raw/c543f1c60eec6c115bd3d1d97fa45c4bb8b3e573/reproducer.sh

You can test it yourself in a temporary, junk folder. It's meant to be run in parallel (4 at once) to try to trigger the bug.

Here is his post for reference:

some copied files are corrupted (chunks replaced by zeros) · Issue #15526 · openzfs/zfs

System information Type Version/Name Distribution Name Gentoo Distribution Version (rolling) Kernel Version 6.5.11 Architecture amd64 OpenZFS Version 2.2.0 Reference https://bugs.gentoo.org/917224 ...

github.com

Apparently, someone was able to consistently reproduce the bug on TrueNAS Core 13.0-U5.3, ZFS 2.1.11.

I might spin this up myself. Tomorrow might not be feasible though.

This type of bug in ZFS really worries me.

We'll investigate.. but so far we don't have confirmation of a real issue in TrueNAS.

 

[Patrick M. Hausen]

But, if I click the link for the release notes from the System / Update in the TrueNAS-13.0-U5.3 UI, the link takes me to a Nightly Version Notes page

Yes. That's a bug.

 

[Juan Manuel Palacios]

A "reproducer" script was created in the discussion by Tony Hunter.

https://gist.githubusercontent.com/tonyhutter/d69f305508ae3b7ff6e9263b22031a84/raw/c543f1c60eec6c115bd3d1d97fa45c4bb8b3e573/reproducer.sh

You can test it yourself in a temporary, junk folder. It's meant to be run in parallel (4 at once) to try to trigger the bug.

Here is his post for reference:

some copied files are corrupted (chunks replaced by zeros) · Issue #15526 · openzfs/zfs

System information Type Version/Name Distribution Name Gentoo Distribution Version (rolling) Kernel Version 6.5.11 Architecture amd64 OpenZFS Version 2.2.0 Reference https://bugs.gentoo.org/917224 ...

github.com

Apparently, someone was able to consistently reproduce the bug on TrueNAS Core 13.0-U5.3, ZFS 2.1.11.

I might spin this up myself. Tomorrow might not be feasible though.

This type of bug in ZFS really worries me.

Yes, it is a very nasty bug, and all of a sudden I'm now also scared for my data, after having read to the current end of the comments in that Github issue, because my system matches one that reproduced the problem (zfs-2.1.11-1).

We'll investigate.. but so far we don't have confirmation of a real issue in TrueNAS.

Is there any potential mitigation you'd recommend at this point? ZFS developers on that issue talk about setting zfs_dmu_offset_next_sync to 0 as their current best guess to avoid the problem entirely, and I'm guessing on FreeBSD that translates into setting the vfs.zfs.dmu_offset_next_sync sysctl variable to 0.

Is that correct? Is that something you recommend? Or is there a reason we may not want to mess with that sysctl variable?

Thank you in advance!