Bug 43032 - Activate no_mbcache by default
Activate no_mbcache by default
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Kernel
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on: 41054
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-22 13:35 CET by Stefan Gohmann
Modified: 2019-01-03 07:23 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few 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.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2016-11-22 13:35:58 CET
We should consider to activate no_mbcache by default, at least for new installed systems.

+++ This bug was initially created as a clone of Bug #41054 +++

UCS Version 4.1-1

Ticket#2015091521000246 #24: "NMI watchdog: BUG: soft lockup – CPU#0 stuck for 22s! [smbd:8822]"

https://bugzilla.kernel.org/show_bug.cgi?id=107301
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2016-11-23 16:05:56 CET
As of UCS@school 4.1R2v5 (Bug #40347) the netlogon share has been placed outside of the sysvol share. Logon scripts are also created in the netlogon share:

samba/share/netlogon/path=/var/lib/samba/netlogon
ucsschool/userlogon/netlogon/path=/var/lib/samba/netlogon/user

This applies only for fresh installations. So old installations are not changed automatically.

So the mbcache problem should only affect old UCS@school systems. Therefore activating no_mbcache would give no benefit on new UCS@school systems.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:23:32 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.