I have attached replacement for vfs_ixnas for 13.0-U1 to this post.
WARNING: This is only for 13.0-U1. Using on an incorrect version of TrueNAS may cause smbd service to refuse connections.
Steps to apply:
1. Stop SMB service
2. Either clone current boot environment or make a copy of
/usr/local/lib/shared-modules/vfs/ixnas.so
3. Extract attached zip
4. replace
/usr/local/lib/shared-modules/vfs/ixnas.so
with one from zip
5. Start SMB service
Steps to revert:
1. Stop SMB service
2. Copy stored old version of ixnas.so to
/usr/local/lib/shared-modules/vfs
3. Start SMB service
Hashes (generated with `sha256` command on TrueNAS 13):
SHA256 (ixnas.so) = 7f20d35bd00c983efa6ed7ceba0db75119641b6c75a800866486bfee067db20b
^^^ New version
SHA256 (ixnas.so) = 4821e9089bc23e1cbea853e215204f60f78e13810864a2610b633f3801e1c75b
^^^ Original version
How to verify it's working:
1. Find path within SMB share that is affected (no SYNCHRONIZE bit set)
2. Run smbcacls command with appropriate arguments to see ACL on path.
Example:
smbcacls //127.0.0.1/SHARE stuff -U smbuser%Cats -j | jq
This will pretty-print JSON-formatted ACL of path "stuff" within the share "SHARE" authenticating with user "smbuser" with password "Cats".
You should see `synchronize: true` on all ALLOW entries (regardless of what is set in local FS ACL).
Like any shell commands, escaping or quoting path may be required.
Commit in our samba repo:
https://github.com/truenas/samba/commit/6e1bae5a4589b500eb69302ff3ea08e3d2e9dff8
NOTE: if you run into an issue with these steps, please PM me and I will figure out what went wrong and edit this post accordingly.