I have recently moved my pictures from a dying drobo to a TrueNAS storage server connected via a 100GbE network NFS mount. I am using Lightroom Classic (13.2) on Windows 11. My Lightroom catalog and views are on a local NVME SSD but I have so many photos in my catalog that I have outgrown most local NAS options.
I am seeing an issue processing my files with either Lightroom's internal Denoise feature or using Topaz's PhotoAI to process a photo or group of photos (with the created dng file.) The dng file will get created in either case, but Lightroom will flag the picture with an error (exclamation point Screenshot 1). If you try to Retry the Metadata Save, you get an error that you only have read access to the file (Screenshot 2.)
If you look at the file properties on the NFS share on the TrueNAS server, they are slightly different between Topaz (555) and Adobe (755) but the Lightroom error is the same. Given that when I copy the NEF files over to the share from Windows, they have 755 properties and Lightroom can import those files and create the XMP files fine (which also have 755 properties.) I am not surprised the Topaz doesn't work given this, but would expect the Adobe Denoise to be fine.
I can fix this by running chmod 777 on the files/directories on the server which will make Lightroom happy, but that is obviously an annoyance I would like to avoid if I could. Do you have any ideas that I could use to fix this?
More tech details
I have set up the NFS shares in Windows as described here: https://ibexoft.com/mounting-nfs-share-on-windows-10-with-write-access/
My actual mount command in my startup folder is: mount -o anon \\192.168.1.11\mnt\photos S:
My workflow is copy all of my photos off of the memory card(s) to an internal NVME drive where I will select the pictures I'm going to edit/import immediately into LR. I create a new directory on the NFS share (based on my storage naming organization) and move the raw files over to that directory. When those files are moved over to that share their file properties are 755 and owned by the user/group I expect them to be owned by. I can import those files into Lightroom and edit them without issue and the sidecar files are created without issue even though the properties are 755. However, the only way to fix the Lightroom issue I'm seeing is to change the properties to 777. Even 775 doesn't work. Once I change the properties to 777 I can Retry the Metadata Export in Lightroom and Lightroom is happy.
I do use Lightroom on my MacBook Pro and do notice that all of the raw files and XMP files on the Mac have 777 permissions with the local user/group owning the files.
On the TrueNAS server I have tried to set a default umask to 000 for nonlogin accounts by creating a umask.sh in the /ect/profile.d directory, which is what I think should catch any account that I would create in TrueNAS, but I haven't been able to see any change on the server side. Still looking at that side of things as well.
I might try to do a test with a share set up for my Mac to the TrueNAS server to see if the behavior is different from the Mac version of LR compared to Windows. Wouldn't be surprised if that was the case.
Looking for ideas on how to get around this.
Let me know if you need any other data. Thanks.
AdChoices
