That's an interesting endorsement. I've been burned so many times by index or table corruption due to SMB issues that it's been really hard to trust MS when they say "No, really. We've fixed it this time."
-- rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dave Crozier Sent: Wednesday, March 11, 2015 4:21 AM To: profoxt...@leafe.com 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:profox-boun...@leafe.com] On Behalf Of Alan Bourke Sent: 10 March 2015 14:52 To: profox@leafe.com; profoxt...@leafe.com 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: ProFox@leafe.com 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/cy1pr10mb0218865e7f7716efa013d069d2...@cy1pr10mb0218.namprd10.prod.outlook.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.