Holger Hegmanns
2008-Sep-29 23:38 UTC
[Samba] strang locking behaviour with macosx clients
I'm running a samba pdc on my gentoo box in a mixed environment with a couple of Windows XP clients and only a few MacOSX clients. The users told me, the file locking across the platforms does not work properly sometimes. I tried to google my problem, but without luck. I switched all the flags related the lock mechanism of samba on and off, but the problem seems to be solved yet. The only debug information I have is the output of smbstatus. The column "DenyMode" looks totally different if a mac or a windows client opens the same file. A *windows* client opens a file: [...] Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 19919 501 DENY_ALL 0x2019f RDWR EXCLUSIVE+BATCH /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:50:24 2008 19919 501 DENY_WRITE 0x20089 RDONLY EXCLUSIVE+BATCH /data0/prod test.indd Tue Sep 30 00:50:24 2008 A *mac* client opens a file: [...] Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 19564 501 DENY_NONE 0x20007 RDWR NONE /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:51:43 2008 19564 501 DENY_NONE 0x20001 RDONLY NONE /data0/prod test.indd Tue Sep 30 00:51:43 2008 Believe it or not, but generally windows denies the opening of a file that is already opened on a mac. Any help is appreciated. Sorry for my poor english.
2008/9/29 Holger Hegmanns <hlx@jungle-world.com>:> I'm running a samba pdc on my gentoo box in a mixed environment with a > couple of Windows XP clients and only a few MacOSX clients. The users > told me, the file locking across the platforms does not work properly > sometimes. > > I tried to google my problem, but without luck. I switched all the flags > related the lock mechanism of samba on and off, but the problem seems to > be solved yet. > > The only debug information I have is the output of smbstatus. The column > "DenyMode" looks totally different if a mac or a windows client opens > the same file. > > A *windows* client opens a file: > [...] > Locked files: > Pid Uid DenyMode Access R/W Oplock > SharePath Name Time > -------------------------------------------------------------------------------------------------- > 19919 501 DENY_ALL 0x2019f RDWR > EXCLUSIVE+BATCH /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:50:24 2008 > 19919 501 DENY_WRITE 0x20089 RDONLY > EXCLUSIVE+BATCH /data0/prod test.indd Tue Sep 30 00:50:24 2008 > > A *mac* client opens a file: > [...] > Locked files: > Pid Uid DenyMode Access R/W Oplock > SharePath Name Time > -------------------------------------------------------------------------------------------------- > 19564 501 DENY_NONE 0x20007 RDWR NONE > /data0/prod ~test~0kjyv(.idlk Tue Sep 30 00:51:43 2008 > 19564 501 DENY_NONE 0x20001 RDONLY NONE > /data0/prod test.indd Tue Sep 30 00:51:43 2008 > > Believe it or not, but generally windows denies the opening of a file > that is already opened on a mac.It's the client's choice which kind of deny mode to use. If the OS X application is happy to use DENY_NONE, then presumably that's correct for that usage. There's no bug here and nothing you can do on the server to alter this behaviour. -- James Peach | jorgar@gmail.com
Apparently Analagous Threads
- gluster rebalance taking three months
- parfm unable to fit models when hazard rate is small
- Healing completely loss file on replica 3 volume
- [LLVMdev] A question w.r.t fence instruction vs. noalias pointer
- [LLVMdev] A question w.r.t fence instruction vs. noalias pointer