- Oplocks allow a client to notify the file server that it will not only be the exclusive writer of a file but will also cache its changes to that file locally to speed up file access.
- When the file server identifies that a file has been opportunistically locked by a client, it marks its version with an opportunistic lock and waits for the client to complete work on the file.
An example of a UEM logfile that shows delays during logon can be found below:
2018-05-29 10:33:04.015 [INFO ] Config file '\\EMC_Isilon\UEM_CONFIG\General\Applications\Notepad++.ini' added to DirectFlex cache
2018-05-29 10:33:14.031 [INFO ] Config file '\\EMC_Isilon\UEM_CONFIG\General\Applications\Notepad.INI' added to DirectFlex cache
2018-05-29 10:33:24.019 [INFO ] Config file '\\EMC_Isilon\UEM_CONFIG\General\Applications\Paint.INI' added to DirectFlex cache
2018-05-29 10:33:34.015 [INFO ] Config file '\\EMC_Isilon\UEM_CONFIG\General\Applications\PaintDotNet.ini' added to DirectFlex cache
2018-05-29 10:33:44.004 [INFO ] Config file '\\EMC_Isilon\UEM_CONFIG\General\Applications\Edit.INI' added to DirectFlex cache
2018-05-29 10:33:54.008 [INFO ] No profile archive to import for config file '\\EMC_Isilon\UEM_CONFIG\General\Applications\PuTTy.INI'
When you experience this issue you would typically see delays between processing of each file (as you can see the 10-second delay between each file process in the example above).