Getting Permanent Write Permission On SMB afterwards

ed1k · 6. Juni 2014

Hi,

i have configured my OMV with filesystems, SMB and so one. But when i download any new file, i can´t delete it. I always have to change ACL-Settings, then it works. I have got a hint that the problem is, that at first setup i made a mistake when mounting the filesystems with the wrong permissions.

Now my question, how i am able to change the permission, so the user "ed" can always write on smb-shares? In OMV-Web-Gui i can´t unmount/remount my filesystems. What can i do? I don´t want to delete the drives, because i have near 8 Terabyte of Data on it.

Thanks in advance for your help!

Have a nice weekend!

davidh2k · 6. Juni 2014

Code

cd /media/
chown root:users -r *
chmod 775 -r

Check that ed is in the users group, which he should be by default.

Greetings
David

ed1k · 6. Juni 2014

https://www.dropbox.com/s/5up5….06.14%2023%2029%2037.png

davidh2k · 7. Juni 2014

My bad, forgot the '*' and can not remember -R/-r correctly:

Code

chown root:users -R *
chmod 775 -R *

Try again.

Greetings
David

ed1k · 7. Juni 2014

https://www.dropbox.com/s/irod….06.14%2007%2039%2048.png

Dont know why its not working

davidh2k · 7. Juni 2014

It's working. It just can't set the attributes for the aquota dirs which is okay.

Greetings
David

tekkb · 7. Juni 2014

Only the owner of the file can delete it. You need to change ownership to the owner you are connecting with via smb.

change directory so you are inside the folder where you want to change ownership of all files and folders
chown -R (the user you use to connect):users *

so if you user was "ed" you would do this:
chown -R ed:users *

The default settings in the samba config are set like this on purpose. So another user cannot delete the owner's files/folders.

PS- You can always use root via ssh to delete files/folders.

Change directory to where files/folders are located:
rm filename (will remove single file)
rm * (will remove all files in a folder)
rm -rf foldername (to delete a folder and all contents)
rm -rf * (to remove all files and folders recursively, that is all contents)

davidh2k · 7. Juni 2014

This is not the problem. I can delete files from other users just fine via SMB/CIFS. The Problem has to be somewhere else.

Greetings
David

PS: Moved to SMB/CIFS Forum.

Edit: I can even delete such a file just fine via SMB/CIFS:

Code

-rw-r--r--+  1 root  users  11G Mai 26 16:47 Filename.mkv

And no, my User is not part of the root Group.

tekkb · 7. Juni 2014

Check chmod or torrent downloads.

Also David, this is 1 step:
chown -R ed:users *

Your method is 2:
chown root:users -R *
chmod 775 -R *

They both should work...

davidh2k · 7. Juni 2014

Just tested a bit more. If I do not have ACLs configured it does not work. If I use ACLs with applying it to all subfolders etc. and then create a folder + file via CLI that belongs to root:users I can still delete it, no need to apply ACLs again for this new folder. So my guess would be that the torrentfolder that is created does not belong to the users group.

Greetings
David

ed1k · 8. Juni 2014

Now my plex is not working after i made "chown root:users -R *
chmod 775 -R *"

What a you doing guys

/EDIT
I gave the user "admin" and "plex" read/write permissions in ACL for all drives and now Plex works again. Puhh...

ed1k · 11. Juni 2014

Zitat von "tekkbebe"

Only the owner of the file can delete it. You need to change ownership to the owner you are connecting with via smb.

change directory so you are inside the folder where you want to change ownership of all files and folders
chown -R (the user you use to connect):users *

so if you user was "ed" you would do this:
chown -R ed:users *

The default settings in the samba config are set like this on purpose. So another user cannot delete the owner's files/folders.

PS- You can always use root via ssh to delete files/folders.

Change directory to where files/folders are located:
rm filename (will remove single file)
rm * (will remove all files in a folder)
rm -rf foldername (to delete a folder and all contents)
rm -rf * (to remove all files and folders recursively, that is all contents)

Alles anzeigen

Thanks for help, but it did not help:

Code

chown: Zugriff auf „*“ nicht möglich: Datei oder Verzeichnis nicht gefunden
root@NAS:/media/f914a2a1-8aae-4e0b-b9bd-8e779c8c8673/MEDIA_4/_DOWNLOADS# chown -R ed:users *

davidh2k · 12. Juni 2014

Go up one directory and type it like that: (alltough it still should be root:users and not ed:users)

Code

chown -r ed:users _DOWNLOADS

Greetings
David

ed1k · 17. Juni 2014

So it all does not work
This is too complicate for newbies. Maybe the problem is not OMV... its Linux. But its way to complicate. The whole user permission system is just redundant and not working for me.
Now i see the advantages of i.e. Synology or QNAP Systems :roll:

ryecoaaron · 17. Juni 2014

Zitat von "ed1k"

So it all does not work
This is too complicate for newbies. Maybe the problem is not OMV... its Linux. But its way to complicate. The whole user permission system is just redundant and not working for me.
Now i see the advantages of i.e. Synology or QNAP Systems :roll:

Synology and QNAP are both Linux and use samba just like OMV...

That being said, I don't know why you can't get this to work unless the data was already on the drives when you installed OMV.

ed1k · 18. Juni 2014

Zitat von "ryecoaaron"

Synology and QNAP are both Linux and use samba just like OMV...

That being said, I don't know why you can't get this to work unless the data was already on the drives when you installed OMV.

Hi,

yes of course the data was already there, when i installed OMV. Why this is a problem?

ryecoaaron · 18. Juni 2014

If the data was already on the drives, there could be many ACLs/permissions/ownerships involved that don't match the current OMV users/user ids/groups. This could give you lots of permission issues. What filesystem? What were you using before OMV?

ed1k · 18. Juni 2014

Zitat von "ryecoaaron"

If the data was already on the drives, there could be many ACLs/permissions/ownerships involved that don't match the current OMV users/user ids/groups. This could give you lots of permission issues. What filesystem? What were you using before OMV?

Maybe this is the problem, yes.

I use ext4, which i created with gparted. Maybe i have to change permission there?

ryecoaaron · 18. Juni 2014

No, OMV can change the permissions the same way gparted would. Can you post the output of:

cat /etc/samba/smb.conf

ed1k · 18. Juni 2014

Code

/etc/samba/smb.conf
#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
server string = %h server
include = /etc/samba/dhcp.conf
dns proxy = no
log level = 0
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
syslog only = yes
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = yes
aio read size = 16384
aio write size = 16384
null passwords = no
local master = yes
time server = no
wins support = no


#======================= Share Definitions =======================
[MEDIA_3]
path = /media/969f7428-e731-4efd-8b2a-773f2eea3d09//
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "ed","edik"
invalid users = 
read list = 
write list = "ed","edik"


[MEDIA_2]
path = /media/d3c70b57-97da-43dd-bfd2-352bf6bf34f9//
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "ed","edik"
invalid users = 
read list = 
write list = "ed","edik"


[MEDIA_4]
path = /media/f914a2a1-8aae-4e0b-b9bd-8e779c8c8673//
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = yes
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "ed","edik"
invalid users = 
read list = 
write list = "ed","edik"


[MEDIA_1]
path = /media/c3581a6b-6c98-4e10-879f-bf1681cc587e//
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "ed","edik"
invalid users = 
read list = 
write list = "ed","edik"


[omv-data]
path = /media/05f3508d-6afd-43f3-a282-43e4d876b647//
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "ed"
invalid users = 
read list = 
write list = "ed"


root@NAS:~#

Alles anzeigen

Jetzt mitmachen!