Soalo, On Fri, Jul 27, 2012 at 03:17:28PM -0300, Saulo Soares de Toledo wrote: > Aditionally, I have tested at shares: > oplocks = False > level2 oplocks = False > # share modes = no > # locking = no > strict locking = no > blocking locks = no
> Samba manual told us force user + oplocks enabled is a problem, then I have > deactivated it (See "Beware of Force User" at > www.samba.org/samba/docs/man/Samba-HOWTO-Collection/locking.html ) Did you try with oplocks enabled? The manual only says oplock and force user can lead to performance degradation when the network is unreliable. It doesn't say they should never be used together. > "share modes = no" is deprecated and do not worked while activated. The > lockings > are with "no", but the error still... > "locking = no" worked, but some large files are being corrupted, and this > problem is worse than the deny. If you get corruption when you disable locking, there must still be some access from one client while the other one is using the file. Could you describe the exact steps needed to reproduce the problem when locking is enabled? What application are you using? How long after the first client closes the file did you try to access it on the second client? Does it work if the first client disconnects? Or if the first client machine is shut down? What is the output of smbclient when the problem occurs? (please check to see that this output does not contain sensitive information before sending it to the bug report) The fact that you can get access when you disable locking indicates that you don't have a permission issue, but a locking issue. This problem is probably not a debian specific issue. I suspect it is a configuration issue. It might be better to try via the samba mailing list or IRC channel: https://lists.samba.org/mailman/listinfo/samba http://www.samba.org/samba/irc.html > This is definitely not an option, I'm afraid. Quota support *is* > expected from our users. > > How we can remove that erros from samba with quota enabled? I suspect the quota error you are seeing in the log is not related to the locking problem. If you suspect otherwise, you could try to rebuild the samba server without quota support. Cheers, Ivo De Decker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
