OpLock+flat DB corruption (Was: How Samba let us down)
--- [EMAIL PROTECTED] wrote: On Wed, Oct 23, 2002 at 05:25:56AM -0700, Jay Ts wrote: The corruption might be related to oplocks. I'm doing File corruption is treated as a drop everything - priority 1 bug in Samba. If this were a generic problem known with 2.2.6 we'd be issuing a patch *immediately*. OpLocks were indeed causing corruption; we only turned them off, made no other changes, and have no more corruption, as I reported yesterday. Wouldn't that be a priority 1, drop everything bug? Other experience was confirmed by doing a Google, by 2 Samba authors, and by the results of our one simple change. If you'd like, I can submit an official bug report. /dev/idal __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
Re: [Samba] OpLock+flat DB corruption (Was: How Samba let us down)
--- Bradley W. Langhorst [EMAIL PROTECTED] wrote: the oplock problem with access databases is well known... I don't think samba alone can fix it. (somebody prove me wrong :) Samba alone probably cannot fix it. I have since learned it can also be a problem on NT. Jeremy says, file corruption is a drop everything - priority 1 bug, so... A. If its well known, I didn't see it in the manpages, online, or offline docs. B. If its well known and unfixable, it ought to be disabled by default if preventing file corruption is really more important than performance. C. We're not using Access, but large flat databases. D. We don't have multiple users, but multiple processes on multiple servers, so E. If someone had put Access has a problem with OpLocks in the docs, it is doubtful we would have considered it at first. The problem is NOT JUST Access, but apparently any kind of large, flat database file. If preventing file corruption is a drop everything - priority 1 bug (quoting Jeremy), it should either be documented and/or disabled by default. But if performance takes priority over file corruption, at least document it. /dev/idal __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
RE: [Samba] OpLock+flat DB corruption (Was: How Samba let us down)
On Thu, 24 Oct 2002, David Brodbeck wrote: -Original Message- From: Chris de Vidal [mailto:cdevidal;yahoo.com] --- Bradley W. Langhorst [EMAIL PROTECTED] wrote: the oplock problem with access databases is well known... I don't think samba alone can fix it. (somebody prove me wrong :) Samba alone probably cannot fix it. I have since learned it can also be a problem on NT. Jeremy says, file corruption is a drop everything - priority 1 bug, so... We've seen file corruption at our site under both NT and Samba, but in our case it was actually less common with Samba. Eventually we gave up on flat Access mdb files and went with MySQL and linked tables -- this seems to be the only real solution. Access is kind of a toy database by itself, it works just long enough to get you hooked and then it fails when you get more than a few users involved. I had a customer who ran an Access MDB for years with only 5 users. No problems. Then he brought a second office on line. Next day - bang! Datafile munched up (NT4 server!). We migrated to Postgresql - not one problem since. BTW: Using the 32bit ODBC driver for MS Windows, still using the same MS Access application. I do not like MDB files - at all. My $0.02 worth. - John T. -- John H Terpstra Email: [EMAIL PROTECTED]
RE: [Samba] OpLock+flat DB corruption (Was: How Samba let us down)
-Original Message- From: Chris de Vidal [mailto:cdevidal;yahoo.com] --- Bradley W. Langhorst [EMAIL PROTECTED] wrote: the oplock problem with access databases is well known... I don't think samba alone can fix it. (somebody prove me wrong :) Samba alone probably cannot fix it. I have since learned it can also be a problem on NT. Jeremy says, file corruption is a drop everything - priority 1 bug, so... We've seen file corruption at our site under both NT and Samba, but in our case it was actually less common with Samba. Eventually we gave up on flat Access mdb files and went with MySQL and linked tables -- this seems to be the only real solution. Access is kind of a toy database by itself, it works just long enough to get you hooked and then it fails when you get more than a few users involved.
Re: OpLock+flat DB corruption (Was: How Samba let us down)
On Thu, Oct 24, 2002 at 04:43:53AM -0700, Chris de Vidal wrote: OpLocks were indeed causing corruption; we only turned them off, made no other changes, and have no more corruption, as I reported yesterday. Wouldn't that be a priority 1, drop everything bug? Other experience was confirmed by doing a Google, by 2 Samba authors, and by the results of our one simple change. If you'd like, I can submit an official bug report. Is it completely reproducible ? Problems cuased by clients not responding to oplock breaks are notoriously dependent on network hardware and client issues (network drivers etc). We drive the client differently than a Windows TCP stack, and remember Microsoft don't test with anything than their own stack. Problems like this come under the oplock break problems, not generic corruption. Jeremy.
