My advice with Server 2008R2  and later is to leave SMB, oplocks,
leasing and caching alone unless you're forced to mess with them.

-- 
  Alan Bourke
  alanpbourke (at) fastmail (dot) fm

On Tue, 22 Mar 2016, at 10:01 AM, Peter Cushing wrote:
> On 21/03/2016 18:45, Tracy Pearson wrote:
> > We host our data on a Server 2012 with application being run from 
> > Server 2008 accessing the data. We get CDX corruption. Some clients 
> > more than others. We have a nightly routine to index troubled clients 
> > data sets. Since you asked this. I'm starting some research to see 
> > which files get corrupt the most. There might be a pattern to our 
> > corruption, and a pattern to the code that touches the files. 
> Thanks for the responses.
> 
>  From what I've been reading the problems with SMB were version 1 and 
> early version 2, although there is a lot of conflicting advice out 
> there, even on mircosoft sites.   As far as I can see later versions 
> should be ok on the opportunistic locking/caching front.  Found a few 
> people who recommended turning off server leasing:
> 
> https://social.technet.microsoft.com/Forums/windowsserver/en-US/7336d31b-6c24-468a-9c47-750244ae3a8c/moved-to-server-2012-getting-access-database-corruption
> 
> 
> A couple of suggestions from the site:
> 
> The solution here is to leave SMB2/3 enabled but disable leasing. 
> Leasing is just an enhanced form of OpLocks.
> 
> Here is the registry entry that needs to be added to disable server 
> leasing for SMB2.1.  You will need to reboot after setting this entry.
> 
> Key: 
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
> Value:  DisableLeasing
> Type:  DWORD
> Data:  0x1
> 
> ---------------------------------------------------------
> 
> We migrated from a Windows 2008 file server cluster with four nodes to a 
> Windows 2012 R2 file cluster with two nodes.  After the migration to the 
> new file server cluster our customers running Windows 7 SP1 started 
> reporting Access Database corruption and slow file access.  However, if 
> the SAME Access Database file was hosted on a Windows 2012 R2 file 
> server NOT in a cluster there was no corruption.  I will not bore you 
> with all the tests we ran while trying to determine the cause but here 
> is what we did to fix the issue.  The solution was provided via an open 
> case with Microsoft.
> 
> 1. Create the following registry entries on all Windows 2012 R2 Servers 
> in the new file server CLUSTER and reboot.
> 
> Key: 
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
> 
> Value:  DisableLeasing
> 
> Type:  DWORD
> 
> Data:  0x1
> 
> We have put this change on and will see how it goes.
> 
> Thanks,
> 
> Peter
> 
> 
> This communication is intended for the person or organisation to whom it
> is addressed. The contents are confidential and may be protected in law.
> Unauthorised use, copying or disclosure of any of it may be unlawful. If
> you have received this message in error, please notify us immediately by
> telephone or email. 
> 
> www.whisperingsmith.com
> 
> Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3
> 1RR. 
> Tel:0161 831 3700 
> Fax:0161 831 3715 
> 
> London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
> 
> 
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/1458674340.2381773.556762202.61812...@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to