Arch Linux

Jphillips

Member

Registered: 2019-08-23

Posts: 68

[Solved] Root user unable to write to specific folder on mounted drive

I have a SAMBA network drive being mounted on startup using systemd, with r/w access for all users within a specific group. This generally works fine, but for some reason a specific folder on this drive no longer has write access, even when logged in as root, but also when logged in as the file owner or a member of the group. The permissions seem fine:

# ls -al
total 29705
drwxrwxr-x 2 trp ucn       0 May 23 00:18 .
drwxrwxr-x 2 trp ucn       0 May 29 13:02 ..
-rw-rw-r-- 1 trp ucn 6281422 May  1 22:18 binomial_file.txt

If I try to create a new file in the directory or modify the existing file I get a permissions error:

# touch text.txt
touch: cannot touch 'text.txt': Permission denied

The only thing I can think of it it's an issue with the mount options, which are currently set as:

user=XXXX,rw,uid=trp,gid=ucn,dir_mode=0775,file_mode=0664

What's weird is this works on all other files in the directory, with multiple different users in the ucn group having no issues at all. It's just this one folder that is giving problem....

Last edited by Jphillips (2024-05-31 09:11:49)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 70,981

Re: [Solved] Root user unable to write to specific folder on mounted drive

https://wiki.archlinux.org/title/Samba#Manual_mounting
Have you check ownership and permissions on the server? The directory might also be immutable.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Jphillips

Member

Registered: 2019-08-23

Posts: 68

Re: [Solved] Root user unable to write to specific folder on mounted drive

Thanks, that was in fact the issue. The owner of the folder on the server had been changed, so even though it showed up as r/w when mounted on my computer, it couldn't be written back on the server. Changing the owner (to me) on the server fixed the issues.

Interesting issue -- I'm surprised there was no way to determine this from within my local system. You'd think there'd be some different attribute or something indicating a problem.

Last edited by Jphillips (2024-05-31 09:12:30)