TrueNAS 13.3 CORE Community Contributions

[Patrick M. Hausen]

@Kris Moore I still don't get why there needs to be a truenas/13.3 branch for ports? We "simply" clone ports/2024Q1, throw that in poudriere and then use the packages. Not much babysitting necessary. And we have a couple of hundred packages, too.
Next quarter we switch everything to ports/2024Q2. And so on ...

 

[Kris Moore]

@Kris Moore I still don't get why there needs to be a truenas/13.3 branch for ports? We "simply" clone ports/2024Q1, throw that in poudriere and then use the packages. Not much babysitting necessary. And we have a couple of hundred packages, too.
Next quarter we switch everything to ports/2024Q2. And so on ...

In a world where you use vanilla ports, sure that's fine. We are an appliance. We have to modify and adjust ports to fit TrueNAS needs for CORE. Its not cookie-cutter. Unless you want various things to break for Samba, Rsync, ACLs, etc. Nevermind the work we have to do to stabilize ports once we get into the testing phases. One of our biggest gripes over the years was the fact that so many ports are updated with zero testing upstream. We always bleed on being the first to find and have to troubleshoot bugs, in things like python, crypto libraries, etc, etc. Otherwise you end up with a very unstable product :)

 

[Patrick M. Hausen]

@Kris Moore Mmmh ... we also adjust various options and we update all customer jails monthly to the lastest FreeBSD minor release (releng/x.y) and the latest commits to the quarterly ports branch.

Well, if it was easy, anyone could do it Appreciate the work and the communication about it.

 

[Phil1295]

@Kris Moore Just a question: why the fixes and changes were not pushed to upstream FreeBSD ? It would have helped maintenance over the years, no ?

 

[Kris Moore]

The needs for building and maintaining TrueNAS don't always directly compliment with what an upstream port maintainer wants, nor should it. But we do tend to upstream where it makes sense.

If you are curious, you are welcome to dig through the tree for the upcoming 13.3 to see what's been worked on to get TrueNAS building there.

GitHub - truenas/ports: FreeBSD ports tree

FreeBSD ports tree. Contribute to truenas/ports development by creating an account on GitHub.

github.com

 

[Patrick M. Hausen]

@Kris Moore Any ETA for a working build again? I would like to submit one particular pull request before code freeze but I need a working build to start. Newest nightly is still Feb, 24th.

Thanks!

 

[Kris Moore]

@Kris Moore Any ETA for a working build again? I would like to submit one particular pull request before code freeze but I need a working build to start. Newest nightly is still Feb, 24th.

Thanks!

We JUST got the build fixed this morning. I'd expect nightly images to start showing up in the next day or two.

 

[Samuel Tai]

@Kris Moore, will 13.3 incorporate the latest bhyve fixes? In particular, this FreeBSD bug results in a non-working mouse in the VNC window. See also this discussion on the forum: https://www.truenas.com/community/t...-in-ubuntu-desktop-vm-truenas-core-vm.114973/

 

[Patrick M. Hausen]

@Kris Moore, will 13.3 incorporate the latest bhyve fixes? In particular, this FreeBSD bug results in a non-working mouse in the VNC window. See also this discussion on the forum: https://www.truenas.com/community/t...-in-ubuntu-desktop-vm-truenas-core-vm.114973/

The fix went into releng/13 on January, 28th and is in 13.3-RELEASE, so my guess is: yes. It would need active messing with the source not to incorporate it.

src - FreeBSD source tree

cgit.freebsd.org

 

[Kris Moore]

Yes, its 13.3 release so any bhyve fixes included will come along "For free" :)

 

[Hemidactylus]

Hey, there was a request to update rclone (for Cloud Sync):

TrueNAS 13.3 Wishlist

Any of the many scripts in the Resources area that handle backing up the config would be infinitely better for this purpose than having to deal with TrueCommand. But far better yet would be doing something useful with the backups you've already been making for the past ten years. We're Ok...

www.truenas.com

Version of rclone in TrueNAS-13.0-U6.1: rclone v1.57.0-DEV (2021-11-01)
Last version: rclone v1.66.0 (2024-03-10)
--> lot of bug fixes, security patches, and better cloud providers support.

Documentation

Rclone Changelog

rclone.org

Will it be updated in this release? Thanks.

 

[winnielinnie]

Can we finally just do this already for Core?

[NAS-106603] - iXsystems TrueNAS Jira

ixsystems.atlassian.net

Why does the login page even require a "username"?

I've always pondered the reasoning behind login screens that only accept root (or admin) as a username, yet still require you to type it in every time. Wouldn't it be preferable and quicker to simply require only a password, as "root" is supplied as the default "username"? It's not like you...

www.truenas.com

To this day, it never made sense to have people type in the only acceptable username of "root" whenever they login to the web GUI. All that's needed is the password. (You wouldn't make people redundantly type in the IP address or hostname into a text field at every login, would you? You know why? Because it's pointless.)

This has nothing to do with SCALE. Core does not have the option to change or set the "admin user" account. The only "username" that's accepted in the text field is "root". Therefor, it makes no sense to have people always type it in. Just. Get. Rid. Of. It. Please.

 

[Patrick M. Hausen]

Hey, there was a request to update rclone (for Cloud Sync):

TrueNAS 13.3 Wishlist

Any of the many scripts in the Resources area that handle backing up the config would be infinitely better for this purpose than having to deal with TrueCommand. But far better yet would be doing something useful with the backups you've already been making for the past ten years. We're Ok...

www.truenas.com

Version of rclone in TrueNAS-13.0-U6.1: rclone v1.57.0-DEV (2021-11-01)
Last version: rclone v1.66.0 (2024-03-10)
--> lot of bug fixes, security patches, and better cloud providers support.

Documentation

Rclone Changelog

rclone.org

Will it be updated in this release? Thanks.

FreeBSD port is at the same version, so definitely possible: https://www.freshports.org/net/rclone/

 

[anodos]

FreeBSD port is at the same version, so definitely possible: https://www.freshports.org/net/rclone/

The ports tree is based on 2024Q1. https://github.com/truenas/ports. There's nothing really secret.

 

[anodos]

https://download-core.sys.truenas.net/

13.3 nightly should be available here. SMB is still WIP I have to add VFS handling for btime and a few other minor things.

 

[Hemidactylus]

The ports tree is based on 2024Q1. https://github.com/truenas/ports. There's nothing really secret.

Ok, so it will be based on rclone v1.65.1, not v1.66.0. So we will not benefit from all the great updates on bisync by Niel from v1.66.
They are only on FreeBSD:13:latest, not quarterly.

 

[grahamperrin]

Would this be of interest to users, or too obscure/esoteric?

zfs list: add '-t fs' and '-t vol' options · openzfs/zfs@a5a7254

 

[grahamperrin]

FreeBSD bug 277717 – kernel using 100% CPU in arc_prune in 13.3

• apparently new (i.e. not triaged), I should ignore the status there in this case
• at least one person in re@ should be aware via <https://old.reddit.com/comments/1bqpxt0/-/kx5jw7d/>
• reportedly affects many people, I can not confirm (I use CURRENT, not releng, to the best of my knowledge I'm not bugged).

Related <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275594#c69> mentions D44170 - D44178, I have not attempted to digest things beyond that point.

<https://reviews.freebsd.org/D44170> … <https://reviews.freebsd.org/D44178>

---

Continued (2024-04-25): <https://forums.truenas.com/t/-/195/10>