zoggy Posted January 19, 2016 Share Posted January 19, 2016 just upgraded from 5.x to 6.x. everything appears to be in order.. running stock unraid (no docker/vm/plugins). i just let sonarr do its thing and checked the file after it was done.. noticed that on 5.x the file resulted in 666: -rw-rw-rw- but now on 6.x its resulting in 676: -rw-rwxrw-+ Looking into also what the trailing + mean.. I found: The "+" indicates that there is an ACL (Access Control List) entry associated with the file. unraid/cache drive are both in reiserfs format. Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 just to note that i do have a cache drive and the files were on cache, ran mover. permissions remain unchanged. ran stat on a file from unraid v5: Access: (0666/-rw-rw-rw-) Uid: ( 1000/ zoggy) Gid: ( 100/ users) ran stat on a file from unraid v6: Access: (0676/-rw-rwxrw-) Uid: ( 1000/ zoggy) Gid: ( 100/ users) Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 file copied to unraid v5: getfacl Scorpion.S02E13.mkv # file: Scorpion.S02E13.mkv # owner: zoggy # group: users user::rw- group::rw- other::rw- file copied to unraid v6: getfacl Scorpion.S02E14.mkv # file: Scorpion.S02E14.mkv # owner: zoggy # group: users user::rw- user:zoggy:rw- group::rw- group:users:rw- mask::rwx other::rw- confirmed no domain/ad: wbinfo -u Error looking up domain users wbinfo -g failed to call wbcListGroups: WBC_ERR_WINBIND_NOT_AVAILABLE Error looking up domain groups Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 rebooted box, formatted cache drive (RFS->XFS), started unraid.. running test file... same thing while copying the file I see the permissions are is correct (666) but when it finishes it gets set to (676).. tried turning off cache drive.. no help. Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 copied files manually and files are good. so looks like the issue is with sonarr.. but now to figure out why on unraid v5 it results in 666 but in v6 it results in 676 with acl... when dropping the extended acl from the file, it sets the permissions back to default (666): setfacl -b filename copied a few files over manually, permissions are good. now went into sonarr and asked it to rename on of the files.. now bad permissions. so deff is sonarr causing the problem during its renaming... wish there was a 'debug' on unraid to see what commands is being processed the commands being processed from sonarr on file name causes an extended acl to be written on the file, now why does it do this on 6.x but not on 5.x.. is it an issue with sonarr? issue with unraid/upgrade? user error (bad setting / kept a .cfg I shouldnt)? Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 thinking there is some sort of smb change from unraid 5 vs 6 thats allowing the acl to be written now.. looking at v6 settings now: /usr/local/sbin# cat /etc/samba/smb.conf [global] # configurable identification include = /etc/samba/smb-names.conf # log stuff only to syslog log level = 0 syslog = 0 syslog only = Yes # we don't do printers show add printer wizard = No disable spoolss = Yes load printers = No printing = bsd printcap name = /dev/null # misc. max protocol = SMB3 invalid users = root unix extensions = No wide links = Yes use sendfile = Yes aio read size = 0 aio write size = 0 # ease upgrades from Samba 3.6 acl allow execute always = Yes # hook for user-defined samba config include = /boot/config/smb-extra.conf # auto-configured shares include = /etc/samba/smb-shares.conf /usr/local/sbin# cat /etc/samba/smb-names.conf # Generated names netbios name = husky server string = i'm not fat hide dot files = no security = USER workgroup = WORKGROUP local master = no map to guest = Bad User passdb backend = smbpasswd encrypt passwords = Yes null passwords = Yes map archive = No map hidden = No map system = No map readonly = Yes create mask = 0777 directory mask = 0777 /usr/local/sbin# cat /etc/samba/smb-shares.conf [flash] path = /boot comment = unRAID Sever OS boot device browseable = no # Private writeable = no read list = write list = zoggy valid users = zoggy map archive = no map system = no map hidden = no map readonly = yes create mask = 0777 directory mask = 0777 [Movies] path = /mnt/user/Movies comment = browseable = yes # Secure public = yes writeable = no write list = zoggy [TV] path = /mnt/user/TV comment = browseable = yes # Secure public = yes writeable = no write list = zoggy Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 creating file smb-extra.conf on flash drive, which I see gets loaded via smb.conf (include = /boot/config/smb-extra.conf). trying older SMB2 to see if it makes a difference.. trying win7's version first.. [global] server max protocol = SMB2_10 client max protocol = SMB2_10 and [global] max protocol = SMB2_10 no luck. Link to comment
trurl Posted January 19, 2016 Share Posted January 19, 2016 One thing seems to be missing from your OP just upgraded from 5.x to 6.x. everything appears to be in order.. running stock unraid (no docker/vm/plugins). i just let sonarr do its thing and checked the file after it was done.. ... Where exactly are you running sonarr if it is not on your unRAID? Link to comment
zoggy Posted January 19, 2016 Author Share Posted January 19, 2016 One thing seems to be missing from your OP just upgraded from 5.x to 6.x. everything appears to be in order.. running stock unraid (no docker/vm/plugins). i just let sonarr do its thing and checked the file after it was done.. ... Where exactly are you running sonarr if it is not on your unRAID? it runs on a windows 7 box in the network. nothing changed on the box it ran on, just unraid... and to update i just found the fix! [global] nt acl support = no so something must have changed in unraid 5 -> 6 where now this is defaulted to on.. if you look at the samba init, "lrwxrwxrwx 1 root root 18 Jan 15 16:49 samba -> /etc/rc.d/rc.samba*" you see that if ADS (active directory services) is enabled.. it defaults this setting to Yes but never explicitly sets it to no otherwise.. for those wanting to see if any acl are set on files.. you can run: getfacl -R -s -p /mnt/user/ | sed -n 's/^# file: //p' if you want to strip the acl you can do: setfacl -b filename Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.