Perms Issue with Samba

[dinjo]

I'm running into a issue where sometimes from a remote device Android phone and tablet I'm not able to delete the files the perms are set to 777 and owner & group owner is set to root still it fails, its sporadic since the file which wasn't able to delete earlier gets deleted after a while.I checked in windows and i saw the folder attributes said Read Only.One thing which i noticed is the data dir shared is showing reading in attached screenshot.Would setting acl check permissions = no , help ?

Below are samba details.
$this->bbcode_second_pass_code('', '
[root@DINJO /etc/samba]$ pacman -Q samba
samba 3.6.3-4
[root@DINJO /etc/samba]$ more smb.conf
[global]
workgroup = WORKGROUP
server string = DINJO
netbios name = DINJO
security = share
load printers = no
printing = bsd
printcap name = /dev/null
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = no
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=131072 SO_SNDBUF=131072 SO_KEEPALIVE
disable netbios = yes
[data]
path = /media/Data/data/torrents
read only = no
create mask = 777
directory mask = 777
public = yes
writable = yes
force user = root
guest ok = yes
')

[dinjo]

?
Would like to know whether its a samba specific issue ?

[doknek]

I am having the same exact issue. Files on samba share cannot be deleted most of the times (works sporadically). This started happening after a recent full update "pacman -Syu". In my case, samba share is being accessed by another xbmc linux machine. File deletions used to work perfectly and they suddenly stopped working. I do not remember modifying smb.conf or file perms or xmbc linux machine. Only thing that might have changed is samba due to pacman full update.

File and directory perm are set to 777 and r+w for group and owner. smb.conf is also set properly to allow deletion of files.

[doknek]

Guys, I solved the problem by downgrading to samba & smbclient 3.6.1.1 from 3.6.4.1. The problem has been fixed as I can delete files.

Doing research on samba forums, I found that other ppl were having a similar problem after the upgrade. So, I downgraded to the last pkg I had in pacman cache using these instructions: https://wiki.archlinux.org/index.php/Do ... g_Packages