I have another Linux system (XBMC Live, based on Ubuntu). I mount my unRAID file server with this line in /etc/fstab:

 

//192.168.1.10/unRAID  /mnt/unRAID  cifs  uid=mrmachine,gid=mrmachine,username=mrmachine,password=mypassword,fmask=644  0  0

 

This makes all files appear to be owned by `mrmachine:mrmachine` and allows the `mrmachine` user on my XBMC machine to write files to the file server (e.g. touch /mnt/unRAID/xyz).

 

But when I log in to the unRAID machine with SSH or telnet and do `ls -la`, I see that the `xyz` file is owned by `mrmachine` (the uid/gid for `mrmachine` is the 1000 on both machines, by coincedence, if it matters). Why isn't unRAID saving the file as `nobody:users`?

 

The problem comes when I try to delete or write to the file from my other machine (a Mac), which I connect to with the same username and password. Because the file is not owned by `nobody:users`, I can't write to or delete it.

 

If I don't include the uid/gid in the fstab line, all files appear to be owned by `root:root` and the `mrmachine` user cannot write to them.

 

Isn't unRAID supposed to use the configured credentials for authentication only, and actually store all files as `nobody:users`?

 

um, I don't know if that is the way it is supposed to be or not.

 

I do know that when I log into my unRAID machine with the user id I created for it (call it bob).  I can see that bob is the owner of the files on the system via the ls -al command.

 

Frankly that is what I would have expected. I am the person that wrote those files there so the ownership of them should belong to me.  Now, depending on how that share is set up other users might have the ability to write and modify those files.

Try using NFS on both machines. Disk Utility can configure NFS auto-mounts. I've been able to resolve blocked write permissions by restarting my Mac.

What happens if you set the uid and gid values in fstab to either the numeric value (1000:1000) or to nobody:users ? Then you have the username and password for authentication..