bakytn
2011-Oct-21 02:06 UTC
[Samba] SAMBA 3.5.11 files opening read only with oplocks = no
Hello! When I'm set oplocks to Yes I'm getting "Oplock break failed for file %s" and files (.doc .xls and .jpg|png etc) take forever to load When I set oplocks to No files opening o.k. but MS Word is saying that they are Read Only. Permissions are 100% fine. The client is Windows 7 Enterprise. Please help.... this is so important to me :( Was it resolved in SAMBA 3.6.x??? I don't dare to upgrade to it yet.. may be it's possible find a workaround? -- View this message in context: http://samba.2283325.n4.nabble.com/SAMBA-3-5-11-files-opening-read-only-with-oplocks-no-tp3924063p3924063.html Sent from the Samba - General mailing list archive at Nabble.com.
bakytn
2011-Oct-21 02:06 UTC
[Samba] SAMBA 3.5.11 files opening read only with oplocks = no
Hello! When I'm set oplocks to Yes I'm getting "Oplock break failed for file %s" and files (.doc .xls and .jpg|png etc) take forever to load When I set oplocks to No files opening o.k. but MS Word is saying that they are Read Only. Permissions are 100% fine. The client is Windows 7 Enterprise. Please help.... this is so important to me :( Was it resolved in SAMBA 3.6.x??? I don't dare to upgrade to it yet.. may be it's possible find a workaround? -- View this message in context: http://samba.2283325.n4.nabble.com/SAMBA-3-5-11-files-opening-read-only-with-oplocks-no-tp3924064p3924064.html Sent from the Samba - General mailing list archive at Nabble.com.
Jeremy Allison
2011-Oct-21 16:27 UTC
[Samba] SAMBA 3.5.11 files opening read only with oplocks = no
On Thu, Oct 20, 2011 at 07:06:32PM -0700, bakytn wrote:> Hello! > > When I'm set oplocks to Yes > > I'm getting "Oplock break failed for file %s" > > and files (.doc .xls and .jpg|png etc) take forever to load > > When I set oplocks to No > > files opening o.k. but MS Word is saying that they are Read Only. > > Permissions are 100% fine. > > The client is Windows 7 Enterprise. > > Please help.... this is so important to me :( > > Was it resolved in SAMBA 3.6.x??? I don't dare to upgrade to it yet.. > > may be it's possible find a workaround?This is usually down to a bad network of some description. Look in the archives. Jeremy.