Trying to delete a file via smb that was created by "nobody" .

I wouldn't think "nobody" should have permissions that should prevent me from deleting.

 

What am I missing

 

 

Try Tools - New Permissions on only that user share.

10 minutes ago, trurl said:

Try Tools - New Permissions on only that user share.

 

I am wondering if this file is in a sub-directory under:    /mnt/user/appdata

 

In which case, there may be a permission issue with a directory somewhere up the tree from this directory.  (OP--- I t is normally recommended not to run new permissions on the appdata share!) 

 

Edited April 22, 20251 yr by Frank1940

29 minutes ago, trurl said:

Try Tools - New Permissions on only that user share.

I dont have my shares broken up into that granularity.

Which under "new permissions" I can't go any deeper then the initial share which would be the entire disk.

 

What does "new permission" do? *edit* it did work

 

19 minutes ago, Frank1940 said:

 

I am wondering if this file is in a sub-directory under:    /mnt/user/appdata

 

In which case, there may be a permission issue with a directory somewhere up the tree from this directory.  (OP--- I t is normally recommended not to run new permissions on the appdata share!) 

 

 

Its not part of appdata entirely seperate disk

 

Edited April 22, 20251 yr by xokia

6 minutes ago, xokia said:

What does "new permission" do?

 

8 minutes ago, xokia said:

Which under "new permissions" I can't go any deeper then the initial share which would be the entire disk.

 

This is setting that you should be using:

You select "Shares" first and then pick the 'Share' (This list of shares is for my server and only the appdata Share will be in your list!)  that contains the file that has the file in it.  Note the warning about running this tool on the appdata share!!!! 

 

If you still have questions be sure to post up your diagnostics file in a new post in this thread. 

How was this file created?

I have a similar problem.
Sabnzbd is creating folders / files the have the owner nobodym and so vie SMB share I am not able to modify this files.
maybbe its a similar problem?

23 hours ago, trurl said:

Try Tools - New Permissions on only that user share.

The problem for me is that I have to do this every day, or twice a day. Can I not get rid of this issue once and for all?

You may have to set the umask in the application to get this fixed. Check the documentation for the application.

From this Post:

 

      https://forums.unraid.net/topic/131730-update-from-69-to-6115-and-got-permission-denied/#findComment-1219731

 

 

here are the settings for Dockers which write to Unraid:

It took me a while to locate this post but here is a short tutorial on getting things setup in a Docker for wrtiing files to Unraid:

 

      https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#comment-1540351

 

Edited April 23, 20251 yr by Frank1940

Thank you trurl and Frank1940. Problem for me is that it isn't a docker app, at least I don't think it is. It is an SMB that I can access and copy, but when I try to move or delete, I get that permissions error. 

Edited April 23, 20251 yr by ag3n7

2 hours ago, ag3n7 said:

It is an SMB that I can access and copy, but when I try to move or delete, I get that permissions error. 

That sentence doesn't explain how it is created.

5 hours ago, ag3n7 said:

The problem for me is that I have to do this every day, or twice a day. Can I not get rid of this issue once and for all?

 

The problem is that whatever is writing this file is probably not doing it through SMB.  (SMB by the way is a protocol for transferring files between computers and is controlled by Microsoft.  Samba is a reverse engineered piece of software used on Unix and Linux computers to emulate the SMB protocol.)  If whatever is creating the file is running in a docker or a VM, it is probably creating this permission problem at the Linux level and those Linux file permissions are not what Samba needs to grant access via SMB.  (Samba is actually an application program that runs on top of the Linux file system and its kernel.  SMB on a Windows client computer runs at the Windows kernel level.)  

 

That is why you keep getting asked how and why these files are being created.  We can't help if all you want to do is to argue that what we are asking about can't be the problem.  If that is true than you must know what the problem is and we who are trying to help are wasting our time...