search for: share_conflict

...ot;stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict: entry->access_mask = 0x100001, entry->share_access = 0x7, entry->private_options = 0x1 [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(392) share_conflict: access_mask = 0x81, share_access = 0x3 [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(441) shar...

...ebug mode appears the messages bellow many times, but it's not so clear for me what does it means, could someone help me ? [2014/10/08 01:44:51.194662, 10, pid=25525, effective(1248, 1012), real(0, 0)] [2014/10/08 01:44:51.194696, 10, pid=25524, effective(1248, 1012), real(0, 0), class=acls] share_conflict: [4] sa (0x7) & share (0x1) = 0x1 [2014/10/08 01:44:51.194805, 10, pid=25525, effective(1248, 1012), real(0, 0)] [2014/10/08 01:44:51.194827, 10, pid=25524, effective(1248, 1012), real(0, 0), class=acls] share_conflict: [5] am (0x100081) & right (0x10000) = 0x0 [2014/10/08 01:44:51.194949...

...9.533052, 10, pid=3350, effective(1017, 1003), real(1017, 0), class=locking] ../source3/locking/locking.c:1226(find_delete_on_close_token) find_delete_on_close_token: name_hash = 0x264a327 [2018/10/12 12:05:09.533062, 10, pid=3350, effective(1017, 1003), real(1017, 0)] ../source3/smbd/open.c:1424(share_conflict) share_conflict: entry->access_mask = 0x100081, entry->share_access = 0x7, entry->private_options = 0x0 [2018/10/12 12:05:09.533070, 10, pid=3350, effective(1017, 1003), real(1017, 0)] ../source3/smbd/open.c:1435(share_conflict) share_conflict: access_mask = 0x100081, share_access = 0x...

Hi! I'm currently hunting a strange problem and looking for help! I have a samba3 fileserver (currently samba-3.0.20b, but problem can be reproduced with samba-3.0.7, but _not_ with samba2 like 2.2.8a), and I see performance problems when writing files with MS word 2002 SP3 from a NT4.0 (SP6a) workstation. Saving even the smallest file takes more than 10 seconds! Copying files with Windows

...locking/locking.c:655(parse_share_modes) parse_share_modes: share_mode_entry[0]: pid = 28903, share_access = 0x7, private_options = 0x200000, access_mask = 0x100180, mid = 0x0, type= 0x0, gen_id = 6, uid = 1000, flags = 0, file_id fe01:2d6001:0 [2011/05/26 15:27:02.145706, 10] smbd/open.c:671(share_conflict) share_conflict: entry->access_mask = 0x100180, entry->share_access = 0x7, entry->private_options = 0x200000 [2011/05/26 15:27:02.145732, 10] smbd/open.c:674(share_conflict) share_conflict: access_mask = 0x2, share_access = 0x7 [2011/05/26 15:27:02.145742, 10] smbd/open.c:683(share_co...

Hello, I have a question because POSIX ACL with SMB2 max protocol does not work properly.Did you test VFS xattr acls with SMB2 max protocol? Is it working corectly? Best regards/Adrian Berlin --

Hello Volker, I was able to get those level 10 logs - spitted by machine. Unfortunately I don't know how attachments behave - Groupwise seems not to be happy with those - so I try the redundant way: Here are the logfiles for this event (only one machine, one try): https://www.bitmammut.de/WDR/log.klnmszap32 In this file there are about 3 occurrences of the

...ould find a solution. Those sharing violations are real, that works as designed for SMB. Applications can request to open files exclusively, and that is what happens here. See for example [2015/06/05 09:49:34.398654, 10, pid=64463, effective(1901, 1901), real(1901, 0)] ../source3/smbd/open.c:1082(share_conflict) share_conflict: check 1 conflict am = 0x120196, right = 0x6, sa = 0x1, share = 0x2 [2015/06/05 09:49:34.398734, 10, pid=64463, effective(1901, 1901), real(1901, 0), class=locking] ../source3/locking/locking.c:652(share_mode_stale_pid) PID 0:27594 (index 0 out of 1) still exists Those messages a...