The Samba-Bugzilla – Bug 8602
Windows7 + Offline Files (+Oplocks) = MSOffice file saving problem
Last modified: 2012-04-27 06:55:51 UTC
Created attachment 7091 [details]
- SLES11SP1 Server with SAMBA 3.5.12 (from Sernet). Samba is configured with just one writable share (see attached config)
- Windows 7 (Enterprise) PC connects to this share and makes is "always available" using offline files (now sync center). With MSOffice 2010 (2007 not tested), we create a new .docx file on the share, make some changes and save it a couple of times to this share.
Lots of XXXXXXX.TMP files created by Office. The docx file is still "seen" by the client, but most likely only due to its offline version, it is not actually on the server.
a) Disable offline files on the client. Then everything is back to normal, but no offline files available :-)
b) Disable oplocks on the server using
oplocks = no
level2 oplocks = no
in smb.conf and restart Samba.
Using a Windows 2008R2 share, the same scenario works fine.
I will provide a level 10 debug log from Samba soon.
Created attachment 7092 [details]
Debug log level 10
Scenario: The Windows 7 client is connected to the share and has it "always available offline".
The debug log starts after the new file "New Microsoft Word Document.docx" has been successfully opened by MS Word. I put some text and hit save (CTRL-S).
The original docx disappears on the server and a file named "1038F1DB.TMP" remains.
Created attachment 7093 [details]
Debug log level 10 with oplocks disabled
Same procedure as before, but with oplocks disabled on the SAMBA side. Now file saving works normally!
Do you get the same problem if you set "kernel oplocks = no" ?
(In reply to comment #3)
> Do you get the same problem if you set "kernel oplocks = no" ?
so I just tested (smb.conf)
kernel oplocks = no
# oplocks = no
# level2 oplocks = no
and I still have the problem. Is that what you meant?
It seems that this issue also exists in 3.6.3.
Is there any workaround?