Ventura: One specific directory locked in an otherwise accessible network share

Question

Ventura: One specific directory locked in an otherwise accessible network share

We have a server running TrueNAS SCALE 24.04.1.1 and one user mounting via 2017 iMac running Ventura that is unable to write media to a directory in a dataset that they require access to.

The user is able to mount all available shares from the NAS, and all but one have no issues. The share with issues, Share1, has four folders at the root. Three of these folders are able to be interacted with, read and written to exactly as expected. The final directory is locked and unable to be accessed by this one user on this one specific network share. I have already confirmed proper network permissions and connection.

The directory and share are both able to be mounted and written to in Windows and macOS on other systems. I have read through the Ventura user guide but was unable to locate any information on permissions or sharing; I'll take another look to make sure I didn't miss anything.

Has anyone had any experience with a similar issue or ideas about potential lanes to look down?

Earlier Mac models

Posted on Jul 8, 2025 8:07 AM

Reply

Answer 1

Top-ranking reply

Tesserax

Level 10

157,734 points

Jul 14, 2025 8:57 AM in response to sumimasenihaveaquestion

Based on what you’ve described, it sounds like this is likely an issue at the macOS client level, not on the TrueNAS end. Since other macOS and Windows clients can access the directory without issue, the NAS is most likely serving the data correctly and permissions are in place.

Ventura has been known to hold onto metadata or xattrs that can conflict with SMB behavior.

On the affected Mac, open Terminal and run: xattr -l /Volumes/Share1/LockedDirectory
If you see any extended attributes that seem out of place, like `com.apple.quarantine`, try: sudo xattr -c /Volumes/Share1/LockedDirectory

Ventura (and earlier macOS versions) sometimes caches network ACLs or misinterprets ACLs that Windows/TrueNAS serve up.

Check from Terminal what permissions the Mac is seeing:

ls -leO@ /Volumes/Share1
ls -leO@ /Volumes/Share1/LockedDirectory

Compare that output with one of the working directories to see if there’s anything odd.

Sometimes macOS stores state or permissions data in hidden files that can cause issues with specific directories.

On the affedted Mac:

sudo find /Volumes/Share1/LockedDirectory -name ".DS_Store" -delete
sudo find /Volumes/Share1/LockedDirectory -name "._*" -delete

These will get rid of Finder metadata and any AppleDouble files that might be conflicting.

Try explicitly forcing SMBv2 (or v3 if needed) on the affected Mac, or disable signing temporarily just to test behavior:

Create or edit `/etc/nsmb.conf` with:

[default]

signing_required=no

smb_neg=smb3_only

Then reboot and remount the share.

Reply