I've just encountered a strange issue where I can create, but not modify, any .dot files on my CIFS shares from a Linux machine.
Running TrueNAS-13.0-U5.1, exporting several CIFS shares to a Linux (Proxmox) server.
Basically it goes like this:
I can then proceed to rm -f the file, which will work fine as well.
What might be the issue that prevents me from writing to a .dot file a second time, but let's me delete it just fine?
This is just a .dot file issue. Normal files that don't start with the "." are working fine.
ACLs and Share permissions all looking good to me - I can perform the same operations natively on the TrueNas server without any issue. It just occurs when doing it via a CIFS mount.
Mount parameters are fairly standard (from /etc/fstab):
Any hint on what else I can check?
I think this started occuring recently, because I noticed it when trying to update my Nextcloud instance. The updater suddenly fails writing it's .step files, which worked perfectly fine when I updated it last time - though that might've been a couple weeks ago.
Running TrueNAS-13.0-U5.1, exporting several CIFS shares to a Linux (Proxmox) server.
Basically it goes like this:
So I can touch the file, then write something to it, but then when I try to write a second time, it fails and I get "permission denied" every time.$ touch /mnt/volume/.test
$ echo test > /mnt/volume/.test
$ echo test2 > /mnt/volume/.test
-bash: /mnt/volume/.test: Permission denied
I can then proceed to rm -f the file, which will work fine as well.
What might be the issue that prevents me from writing to a .dot file a second time, but let's me delete it just fine?
This is just a .dot file issue. Normal files that don't start with the "." are working fine.
ACLs and Share permissions all looking good to me - I can perform the same operations natively on the TrueNas server without any issue. It just occurs when doing it via a CIFS mount.
Mount parameters are fairly standard (from /etc/fstab):
//10.0.0.5/share /mnt/share cifs noauto,x-systemd.automount,x-systemd.mount-timeout=30,_netdev,credentials=/etc/credentials.cred,dir_mode=0750,nosuid,nodev,noexec,noperm,uid=100033 0 0
Any hint on what else I can check?
I think this started occuring recently, because I noticed it when trying to update my Nextcloud instance. The updater suddenly fails writing it's .step files, which worked perfectly fine when I updated it last time - though that might've been a couple weeks ago.