Does this mean that write ahead cache on the disk drive can be safely left
on? And is this win 7 and 8 or just servers?
Al
-----Original Message-----
From: Dave Crozier
Sent: Wednesday, March 11, 2015 9:20 AM
To: [email protected]
Subject: RE: Index Corruption / SMB
+1 for Alan's comment. SMB3 seems to have cured all the cache problems
inherent with SMB1/SMB2
Dave
-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of Alan Bourke
Sent: 10 March 2015 14:52
To: [email protected]; [email protected]
Subject: Re: Index Corruption / SMB
On Tue, 10 Mar 2015, at 02:32 PM, Man-wai Chang wrote:
In addition to un-necessary caching, you also need to disable
opportunistic locking (oplocks) in Samba.
No, you don't. Leave the caching alone. it's there for a reason. If you're
having to mess with caching on a regular basis, you need to be looking at
your program code.
You *can't* turn off OpLocks under SMB2 and SMB3. You have to knock
everything back to SMB1 and then turn off OpLocks which to me is both
unnecessary and a bad idea.
[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/[email protected]
** 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.
