Bug 37253 - Remaining oplocks after win8 hybrid shutdown
Remaining oplocks after win8 hybrid shutdown
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-09 13:04 CET by Tim Petersen
Modified: 2020-07-03 20:54 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2014120521000421
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 Tim Petersen univentionstaff 2014-12-09 13:04:43 CET
Windows 8 implements a "hybrid shutdown" for fastboot per default. This procedure hibernates the kernel part for faster "boot".

This leads to the situation that Oplocks on several profile files (if using roaming profles) are hold even after the system is "shut down".
If you login within 15 minutes (samba default for breaking Oplocks) you get a temp local profile.

A Windows AD Server (2012R2) "recognizes" the situation somehow and breaks an existing Oplock while the user logs in again.


To make this clear: This can only occur under the following cicumstances:
1. User logs in
2. Hybrid-Shutdown
3. Boot
4. Login (steps 2-4 within 15 minutes)
5. -> temp profile

This does NOT happen at reboot, as reboot makes no use of hybrid shutfown and/or fastboot.
Comment 1 Tim Petersen univentionstaff 2014-12-09 13:05:46 CET
2014120521000421
Comment 2 Florian Best univentionstaff 2017-06-28 14:52:25 CEST
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:54:33 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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