Emby users - ref: files permissions

What do you mean by "a samba share controlled by OMV server"?

The short answer is: The user the Emby process runs as must have write permission on the files that are to be deleted.

Adding a user doesn't make a process run as that user or change filesystem permissions.

I suggest not using ACLs unless you really understand what they do.

You still didn't answer my question.

You don't say if Emby is running on the same machine as the files and folders you want it to be able to delete.

What user owns your media files and folders. What is the complete list of permissions on such a typical file and folder?

Emby must be running as a user that has read and write permission on the files and read write and executable permission on the folders.

I don't use VMs here so I have no suggestions about that.

root doesn't own a single file on my system it doesn't need to. What is your use case that needs that?

In the shell, cd into a directory you wish to learn about. Type:

ls -al

This will show you the ownership and permissions, etc.

I can't help you with VMs

Videos is a directory owned by the user root and the group users.

My opinion is that the root user ownership of your Videos folder is a poor choice.

I can't say anything about the files because you haven't shown the permissions and ownership of them yet.

Whatever process you ran to add the files was run as the root user without regard to preserving the ownership and permission attributes, if any existed. Never run anything as the root user unless it must be run that way. Never.

You haven't shown the permissions of any files. What you posted:

Files are the same:

drwxrwsrwx 2 root users

is for a directory.

I don't set permissions using the OMV GUI, I do it by hand in the shell or via highly focused automated scripting. I don't use OMV's ACLs either.

My media folders (more than 29,000) are owned by user fred and group users and have their permissions set to be 2755.

My media files (more than 62,000) are owned by the same user and group as above and have their permissions set to 0644.

If your media collection is organized properly it may be possible to change the ownerships and permissions in a bulk fashion in the shell using a very few specially crafted commands.

I can post what I use to recursively bulk change permissions and ownership of my media files. This will unconditionally modify every file and folder it finds in the directory where it is run from, and within every directory and subdirectory below that one (recursively).

Warning: If you run these commands in the wrong place on your filesystem it doesn't care. There is no way to determine what the permissions and ownership were before they were changed. Make sure you know what you are doing with this.

Run these commands as root in the shell in the order shown. Change the path very carefully to be the starting point from which to make the changes. Change the user and group to agree with your use case. All my media files are in directories immediately below the path shown. The path shown is a mergerfs mount point made up of eight hard drives. But this detail is not important.

I cut these commands out of a shell script. You could create such a script if you think you will need to run this often.

find /srv/dev-disk-by-label-d1/sftp/outgoing/ -type d -exec chmod -R 2755 {} \;

find /srv/dev-disk-by-label-d1/sftp/outgoing/ -type f -exec chmod -R 0644 {} \;

find /srv/dev-disk-by-label-d1/sftp/outgoing/ -type d -exec chown -R fred:users {} \;

find /srv/dev-disk-by-label-d1/sftp/outgoing/ -type f -exec chown -R fred:users {} \;

My media files are located on the same machine that Plex runs on so there are no problems with being able to delete files within Plex - Plex is specifically set up to allow deletions, it is not the default behavior. Plex (like all my dockers) runs as the same user that owns the files, so again, no problems.

I use NFS for file sharing between Linux machines here. I no longer have any Windows machines here. There is user and group ID number equivalence between machines. So being able to modify or delete user owned files across machines just seems to work without any special setup.