samba - Feb 2003 - Samba corrupting files

Hi all,

We use samba here at our site as an interop solution for use with ClearCase.
I'm afraid I'm just a lowly ClearCase administrator not a Unix
administrator.

All our solaris servers are running Solaris 8 and we're using Samba version
2.2.2

First Question :
Our Unix Admin guy has said that we can't upgrade our version of Samba as
2.2.2 is the latest version that Sun have fully tested and compiled binaries
for.  Is this right??  Is there something wrong with the binaries on the
samba website or building it from source??


Second Question :

We're now getting corrupt files appearing in ClearCase.  The files are in
tact except for a number of lines added to the beggining of the file.  Lines
you would normally expect to find in the samba logs.

For example,

[2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
  spark1j opened file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
read=Yes write=Yes (numopen=1)
[2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
  spark1j opened file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
read=Yes write=No (numopen=2)
[2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
  spark1j closed file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
(numopen=1) 
[2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)


Having checked the log file creating for this specific client I find errors
like this....

  Allowed connection from  (172.29.58.57)
[2003/02/26 13:35:22, 0] rpc_client/cli_netlogon.c:cli_net_auth2(160)
  cli_net_auth2: Error NT_STATUS_ACCESS_DENIED
[2003/02/26 13:35:22, 0] rpc_client/cli_login.c:cli_nt_setup_creds(72)
  cli_nt_setup_creds: auth2 challenge failed
[2003/02/26 13:35:22, 0]
smbd/password.c:connect_to_domain_password_server(1371)
  connect_to_domain_password_server: unable to setup the PDC credentials to
machine JENKINS. Error was : NT_STATUS_ACCESS_DENIED.
[2003/02/26 13:35:22, 0] smbd/password.c:domain_client_validate(1591)
  domain_client_validate: Domain password server not available.
[2003/02/26 13:35:22, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(171)
  startsmbfilepwent_internal: unable to open file
/usr/local/samba/private/smbpasswd. Error was No such file or directory
[2003/02/26 13:35:22, 0] passdb/pdb_smbpasswd.c:pdb_getsampwnam(1368)
  unable to open passdb database.
[2003/02/26 13:35:22, 1] smbd/password.c:pass_check_smb(546)
  Couldn't find user 'spark1j' in passdb.
[2003/02/26 13:35:22, 2] smbd/reply.c:reply_sesssetup_and_X(970)
  NT Password did not match for user 'spark1j'!
[2003/02/26 13:35:22, 2] smbd/reply.c:reply_sesssetup_and_X(980)
  Defaulting to Lanman password for spark1j
[2003/02/26 13:35:22, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(171)
  startsmbfilepwent_internal: unable to open file
/usr/local/samba/private/smbpasswd. Error was No such file or directory
[2003/02/26 13:35:22, 0] passdb/pdb_smbpasswd.c:pdb_getsampwnam(1368)
  unable to open passdb database.
[2003/02/26 13:35:22, 1] smbd/password.c:pass_check_smb(546)
  Couldn't find user 'spark1j' in passdb.
[2003/02/26 13:35:22, 1] smbd/reply.c:reply_sesssetup_and_X(995)
  Rejecting user 'spark1j': authentication failed
[2003/02/26 13:35:22, 0] rpc_client/cli_netlogon.c:cli_net_auth2(160)
  cli_net_auth2: Error NT_STATUS_ACCESS_DENIED
[2003/02/26 13:35:22, 0] rpc_client/cli_login.c:cli_nt_setup_creds(72)
  cli_nt_setup_creds: auth2 challenge failed
[2003/02/26 13:35:22, 0]
smbd/password.c:connect_to_domain_password_server(1371)
  connect_to_domain_password_server: unable to setup the PDC credentials to
machine JENKINS. Error was : NT_STATUS_ACCESS_DENIED.
[2003/02/26 13:35:22, 0] smbd/password.c:domain_client_validate(1591)
  domain_client_validate: Domain password server not available.
[2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
  spark1j closed file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
(numopen=1)
[2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
  spark1j opened file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
read=Yes write=No (numopen=2)
[2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
  spark1j closed file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
(numopen=1)
[2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
  spark1j closed file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
(numopen=1)
[2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
  spark1j opened file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
read=Yes write=No (numopen=2)
[2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
  spark1j closed file spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
(numopen=1)
[2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
[2003/02/26 13:39:49, 0] lib/fault.c:fault_report(40)
  ==============================================================[2003/02/26
13:39:49, 0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 11 in pid 24105 (2.2.2)
  Please read the file BUGS.txt in the distribution
[2003/02/26 13:39:49, 0] lib/fault.c:fault_report(43)
  ==============================================================[2003/02/26
13:39:49, 0] lib/util.c:smb_panic(1055)
  PANIC: internal error


Can someone help?? Is this a bug with Samba? or a different issue??
Apologies for sending so much of the log file.

Many Thanks,

Robin Parker

--- "Parker, Robin" <robin.parker@nectech.co.uk>
wrote:
> We're now getting corrupt files appearing in
> ClearCase.  The files are in
> tact except for a number of lines added to the
> beggining of the file.
I can't explain that type of corruption, but I can
suggest you disable all oplocks.  In your smb.conf
global section, 'kernel oplocks = No', and on each
share specify 'oplocks = No' and 'level2 oplocks No'.

I'm not a member of the Samba team but a Linux
administrator whose primary responsibility is several
Samba servers.  We had corruption on several large
flat database files.  When we disabled all oplocks,
our databases no longer corrupted.

I've not been able to test which oplock setting of the
three was causing this problem (or if it was all
three) so I suggest you try disabling them all at once
and then gradually re-enabling them one at a time.  If
that doesn't fix it, be sure to set them back, as
oplocks are a performance boost.

Good luck,
/dev/idal

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

> The files are in tact except for a number of lines
> added to the beggining of the file.  Lines
> you would normally expect to find in the samba logs.
> 
> For example,
> 
> [2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
>   spark1j opened file 
> spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
> read=Yes write=Yes (numopen=1)
> [2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
>   spark1j opened file 
> spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
> read=Yes write=No (numopen=2)
> [2003/02/26 13:39:49, 2] smbd/close.c:close_normal_file(206)
>   spark1j closed file 
> spark1j.vws/.s/00050/8000a1003e445e9dpcp_comp.000
> (numopen=1) 
> [2003/02/26 13:39:49, 2] smbd/open.c:open_file(214)
Do you have write cache enabled?  If so, this is a bug that was found
and the patch is in 2.2.6.
http://marc.theaimsgroup.com/?l=samba&m=103702746209159&w=2

( original thread:
http://marc.theaimsgroup.com/?l=samba&m=103364241422123&w=2 )

~ Daniel









-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.