File changes not being written immediately

Rashkae git at
Fri Mar 23 23:31:21 GMT 2001

Sounds like opportunistic locking (oplocks). When a client requests an
oplock, the server grants that client exclusive use of the file. The
client uses that "exclusive" permission to cache the file locally. (if a
second client requests the file, the server sends a message to the first
client to release the lock, in which case it has to write all changes to
the server and abandone the local cache.)

More information about the samba mailing list