Steven,
LockViolationDelayOffset is the file offset beyond which locks are always
issued as delayed locks. Default value is 0xEF00. Please let us know if
you have any more questions.
Thanks!
Hongwei
From: Steven Danneman [mailto:steven.danne...@isilon.com]
Sent: Monday, December
Hi, Steven,
For the error returned when a byte range lock conflicts with an
existing lock in SMB, the logic is as follows:If a lock request is above a
configured offset, or if a lock request matches a previously failed lock
offset, it will change it from fail immediately with
Hey Hongwei,
That's very interesting and indeed explains the behavior I've seen.
I can understand the motivation for delaying a small timeout for locks
that the server knows are already held. However, the Offset =
LockViolationDelayOffset is strange to me. I don't understand the
Steven,
I am now working on this issue. I am wondering what program you ran to
create the network trace attached in your e-mail. Is it Samba smbtorture ?
If we can duplicate the behavior, it may be easier for us to debug it.
Thanks!
Hongwei
From: Steven Danneman
Hi Steven,
Thanks for your question regarding SMBv1 LockAndX. One of the Open
Specification Documentation team will be in touch with you soon.
Best regards,
Tom Jebo
Open Specification Documentation Support
From: Steven Danneman [mailto:steven.danne...@isilon.com]
Sent: Wednesday, November
