The Fresh Prince of Darkness
2003-May-16 17:25 UTC
[Samba] Oplocks on Windows Clients and Winbind revisited
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First, the more I read about olocks the more inclined I am to disable them globally. Here's the issue though, after experiencing data corruption in Act files at the hands of oplocks, we checked the Act support database and they recommended disabling oplocks not only on the server, but on the client machine as well. Is there any reason why this should be necesary? If I disable oplocks for all my shares, should I disable it on my client machines as well. We're using NT & 2k mostly, with an occasion xp or 98 box, but not many. Also, last week I'd asked about syncing winbind databases. It was suggested that backing up the winbind_idmap.tdb would be sufficient to restore the proper mappings upon failure. I tried an experiment with another linux box wherein as a nightly cron job, the machine shuts down winbind locally and on the master machine, copies the tdb over from the master and then re-starts winbind again. This was successful in reproducing the same mappings as on the master machine. What is the downside to doing this on production servers? Thanks. - -Ron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+xR8ovsPR55EQ+eIRAuZAAJ9IDoKt81AuirAsbBMdLN/KNky1fQCgkrOk m8qBLCBDBIofVuDXE+/xV1M=W9Wh -----END PGP SIGNATURE-----
jra@dp.samba.org
2003-May-16 17:39 UTC
[Samba] Oplocks on Windows Clients and Winbind revisited
On Fri, May 16, 2003 at 01:25:56PM -0400, The Fresh Prince of Darkness wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > First, the more I read about olocks the more inclined I am to disable > them globally. Here's the issue though, after experiencing data > corruption in Act files at the hands of oplocks, we checked the Act > support database and they recommended disabling oplocks not only on the > server, but on the client machine as well. Is there any reason why this > should be necesary? If I disable oplocks for all my shares, should I > disable it on my client machines as well. We're using NT & 2k mostly, > with an occasion xp or 98 box, but not many.Disabling the globally will slow performace. With Samba you can disable them per share or on a wildcard match basis. Jeremy.
Maybe Matching Threads
- Oplocks not taking place at all unless fake oplocks = yes - Update
- Oplocks not taking place at all unless fake oplocks = yes
- oplocks, kernel oplocks, kernel share modes, .. - how it all works?
- oplocks, kernel oplocks, kernel share modes, .. - how it all works?
- oplocks, kernel oplocks, kernel share modes, .. - how it all works?