Bug #9619
closed
SMB operations by some applications with windows 7 clients take an absurdly long time to respond when oplock is enabled
0%
Description
This bug appears to happen in Excel and Word, with Microsoft Security Essentials installed. Microsoft's SMB implementation appears unaffected, and simply disabling oplock, as suggested by this thread (and the linked threads within) seems to eliminate the issue entirely:
Updated by Andrew Stormont about 4 years ago
I suspect this is related to the hangs and timeouts we see when running the Windows Protocol Test Suites against our SMB stack.
Updated by Gordon Ross about 4 years ago
We had this problem (long ago) in our product. The reason for the delay was that the Windows client was failing to respond to an oplock break request (like an NFS cache delegation recall). We opened a case with MS and found that Windows has a minor defect exposed with old-style oplocks (and not exposed with leases) where oplock break request processing on the client may be blocked while another open on the same object is in progress. The advice from MS was basically, "Well, aren't you planning to implement leases?" and that's what we did.
SMB2 leases are there since #11016 integrated. With that integrated, I don't believe this issue is reproducible anymore.
Anyone mind if we just close this? If on the other hand this IS still reproducible, please provide a network capture.
Updated by Gordon Ross about 4 years ago
- Status changed from New to Feedback
- Assignee set to Gordon Ross
Updated by Gordon Ross almost 3 years ago
- Status changed from Feedback to Resolved
Updated by Gordon Ross almost 3 years ago
- Status changed from Resolved to Closed