Bug 41579 – oplocks = no for sysvol and netlogon

Bug 41579 - oplocks = no for sysvol and netlogon


Summary:	oplocks = no for sysvol and netlogon

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:	https://www.samba.org/samba/docs/man/...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-06-15 15:02 CEST by Jens Thorp-Hansen
Modified:	2019-08-01 18:36 CEST (History)
CC List:	3 users (show)

See Also:	9432 41759 49946
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.171
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016061521000455
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jens Thorp-Hansen

2016-06-15 15:02:22 CEST

reference: Ticket#2016061521000455

[netlogon]
level 2 oplocks = no
oplocks = no

[sysvol]
level 2 oplocks = no
oplocks = no

Windows seems to unlock files at shutdown not correctly (as seen in smbstatus -L) - clients are not able to open relevant files right away and need to wait some time.

Comment 1 Arvid Requate

2016-11-09 16:52:53 CET

Pretty interesting thread regarding another workaround (for NT1 only):
 https://lists.samba.org/archive/samba-technical/2011-July/078621.html

Comment 2 Stefan Gohmann

2019-01-03 07:22:39 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.