[Samba] Re: oplock_break and Excel data corruption with Samba 2.2.3a

[Federico Sevilla III]

On Fri, 1 Mar 2002 at 21:31, Federico Sevilla III wrote:
> I checked the Samba logs for her machine and found the following in a
> search for the filename of the Excel file she was working on:

I did some follow-up scans of the Samba logs and found out the following
statistics:

1. Most of the "oplock_break failed" entries are for Excel files but are
not limited to this.

   a. There are 97 logged oplock_break failures. Logs are exclusive to
Samba 2.2.3a installed 2002/02/25, since I flushed the logs during the
upgrade.

   b. Of these, 79 are with Excel files.

      1) 15 are with an installation of Microsoft Excel 2000 on a
Microsoft Windows ME machine, with complete driver updates.

      2) The rest are with installations of Microsoft Windows 97 on
Microsoft Windows 95 OSR2 and 98, also updated, with some almost fresh
installs on new machines.

   c. The remaining 18 are distributed among Word and PowerPoint files.


2. I am not certain if the corruption is caused by the oplock_break
failures. Not all of the files whose modify operations ran into
oplock_break failures are corrupt.


3. Aside from oplock_break, the related "client failure in break -
shutting down this smbd", and authentication failures, the most frequent
errors are related to tdb:

[2002/02/27 14:17:59, 0] smbd/oplock.c:oplock_break(758)
  oplock_break: receive_smb error (Success)
  oplock_break failed for file 2002 JO Masterfile/ProdSched2002Q1.xls (dev = 80a, inode = 62920619, file_id = 2).
[2002/02/27 14:17:59, 0] smbd/oplock.c:oplock_break(843)
  oplock_break: client failure in break - shutting down this smbd.
[2002/02/27 14:17:59, 1] smbd/service.c:close_cnum(653)
  boss (192.168.0.3) closed connection to service jomaster
[2002/02/27 14:17:59, 0] tdb/tdbutil.c:tdb_log(475)
  tdb(/var/run/samba/connections.tdb): remove_from_freelist: not on list at off=9376
[2002/02/27 14:17:59, 0] tdb/tdbutil.c:tdb_log(475)
  tdb(/var/run/samba/connections.tdb): tdb_free: left free failed at 9376
[2002/02/27 14:17:59, 1] smbd/service.c:make_connection(615)
  boss (192.168.0.3) connect to service jomaster as user boss (uid=1001, gid=50) (pid 16809)


   a. This is only an example, though. Not all of the tdb_free errors are
preceded by oplock_break errors.

   b. The oplock_break with the reported data corruption that I sent in my
first post did not have tdb_free errors directly before or after it, or
anywhere relatively near timestamp-wise.

   c. Up to Samba 2.2.3 we ran into severe problems related to tdb.

      1) Something that the logs could not explain (at least to me, at log
level 1) would make Samba grind to a halt, rejecting all new connections
because of max_connection problems.

      2) My latest report on this went unanswered. It had the subject
"rec_free_read bad magic and tdb corruption with Samba 2.2.3":
<http://lists.samba.org/pipermail/samba/2002-February/067485.html>.


That's all I've got for now. I have done my best to detail the whole web
of problems we've been experiencing lately, in the hopes that somehow the
little details will help the developers see the bigger picture and
hopefully pinpoint the root.

Again I request that I be cc'd replies to the thread.

Thank you very much in advance.

 --> Jijo

--
Federico Sevilla III  :: jijo at leathercollection.ph
Network Administrator :: The Leather Collection, Inc.
GnuPG Key: http://jijo.leathercollection.ph/jijo.gpg