Re: [Samba] 3.3.3 blocks writing of files ~1.55GB or greater from Windows XP

2009-04-28 Thread Volker Lendecke
On Tue, Apr 21, 2009 at 09:40:17AM -0500, Nikkos Svoboda wrote:
The logfiles on the Samba server are split by username/hostname. Here is
 a client logfile of an attempt to copy a 2GB file to an empty folder the
 share ( \\shareserver\Sambatest\2GBtestfile.largetest ). There is also an
 smbd logfile, which contains only the statement getpeername failed. Error
 was Transport endpoint is not connected repeated. The series of events for
 this copy compared to a successful copy seem quite different.

I'm afraid that part of the log file is not sufficient, to
me it shows no error.

Volker


pgprzSQvYSWLb.pgp
Description: PGP signature
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] 3.3.3 blocks writing of files ~1.55GB or greater from Windows XP

2009-04-27 Thread Nikkos Svoboda
On Sun, Apr 19, 2009 at 2:17 AM, Volker Lendecke
volker.lende...@sernet.dewrote:

 On Sat, Apr 18, 2009 at 10:35:14PM -0500, Nikkos Svoboda wrote:
 Samba is hosted on a server running Debian-Lenny, on a Reiserfs
  partition.
 
After upgrading to 3.3.3, Windows XP clients fail to copy files
  through explorer using SMB shares when the file size is around 1.55GB or
  greater in size. The error is Cannot copy Filename.ext: The specified
  network name is no longer available. Copying existing files located on
  the share to the same or any other share fails with the same error.
  Copying files from the share to the local client filesystem works
  correctly. Linux and Mac clients have no problems. I have not tested
  Vista at this point.
 
The error occurs before any copying begins. The target folder on the
  share will contain a correctly-named, 0 byte file after the attempt to
  write is made. The POSIX permissions of the 0-byte file on the server
  side are correct and the file is owned by the correct user : group.
 
I do not believe this is related to the error dealing with the
  rotation between ports 139 and 445. The copy does not fail after some
  time, it is immediate. To be sure, I have tried setting both 445 and 139
  alone as the option smb ports = .
 
Is anyone else seeing this behavior?

 Can we see a debug level 10 log of smbd of this problem?

 Thanks,

 Volker


  The logfiles on the Samba server are split by username/hostname. Here is a
client logfile of an attempt to copy a 2GB file to an empty folder the share
( \\shareserver\Sambatest\2GBtestfile.largetest ). The included portion of
the log is about half of the section referring to the file copy, the full
portion is too big for the mailing list. There is also an smbd logfile,
which contains only the statement getpeername failed. Error was Transport
endpoint is not connected repeated. The series of events for this copy
compared to a successful copy seem quite different.

-Nik Svoboda
[2009/04/20 12:51:10, 10] lib/util.c:dump_data(2233)
  [000] 00 5C 00 53 00 61 00 6D  00 62 00 61 00 74 00 65  .\.S.a.m .b.a.t.e
  [010] 00 73 00 74 00 5C 00 32  00 47 00 42 00 74 00 65  .s.t.\.2 .G.B.t.e
  [020] 00 73 00 74 00 66 00 69  00 6C 00 65 00 2E 00 6C  .s.t.f.i .l.e...l
  [030] 00 61 00 72 00 67 00 65  00 74 00 65 00 73 00 74  .a.r.g.e .t.e.s.t
  [040] 00 00 00  ... 
[2009/04/20 12:51:10,  3] smbd/process.c:switch_message(1378)
  switch message SMBntcreateX (pid 12451) conn 0x86e1cb8
[2009/04/20 12:51:10,  3] smbd/sec_ctx.c:set_sec_ctx(324)
  setting sec ctx (XX, XX) - sec_ctx_stack_ndx = 0
[2009/04/20 12:51:10,  5] auth/token_util.c:debug_nt_user_token(528)
  NT user token of user X
  contains 16 SIDs
  SID[  0]: X
  SID[  1]: XX
  SID[  2]: XX
  SID[  3]: XX
  SID[  4]: XX
  SID[  5]: XX
  SID[  6]: XX
  SID[  7]: XX
  SID[  8]: XX
  SID[  9]: XX
  SID[ 10]: XX
  SID[ 11]: XX
  SID[ 12]: XX
  SID[ 13]: XX
  SID[ 14]: XX
  SID[ 15]: XX
  SE_PRIV  0x0 0x0 0x0 0x0
[2009/04/20 12:51:10,  5] auth/token_util.c:debug_unix_user_token(548)
  UNIX token of user XXX
  Primary group is 4 and contains 11 supplementary groups
  Group[  0]: XX
  Group[  1]: XX
  Group[  2]: XX
  Group[  3]: XX
  Group[  4]: XX
  Group[  5]: XX
  Group[  6]: XX
  Group[  7]: XX
  Group[  8]: XX
  Group[  9]: XX
  Group[ 10]: XX
[2009/04/20 12:51:10,  5] smbd/uid.c:change_to_user(303)
  change_to_user uid=(XX,XX) gid=(XX,XX)
[2009/04/20 12:51:10,  4] smbd/vfs.c:vfs_ChDir(733)
  vfs_ChDir to XX ( ### edit - user home directory ### )
[2009/04/20 12:51:10, 10] smbd/nttrans.c:reply_ntcreate_and_X(454)
  reply_ntcreate_and_X: flags = 0x16, access_mask = 0x20189 file_attributes = 
0x80, share_access = 0x7, create_disposition = 0x1 create_options = 0x940 
root_dir_fid = 0x0, fname = Sambatest/2GBtestfile.largetest
[2009/04/20 12:51:10, 10] smbd/open.c:create_file(3283)
  create_file: access_mask = 0x20189 file_attributes = 0x80, share_access = 
0x7, create_disposition = 0x1 create_options = 0x940 oplock_request = 0x3 
root_dir_fid = 0x0, ea_list = 0x(nil), sd = 0x(nil), fname = 
Sambatest/2GBtestfile.largetest
[2009/04/20 12:51:10,  5] smbd/filename.c:unix_convert(148)
  unix_convert called on file Sambatest/2GBtestfile.largetest
[2009/04/20 12:51:10, 10] smbd/statcache.c:stat_cache_lookup(235)
  stat_cache_lookup: lookup failed for name [SAMBATEST/2GBTESTFILE.LARGETEST]
[2009/04/20 12:51:10, 10] smbd/statcache.c:stat_cache_lookup(235)
  stat_cache_lookup: lookup failed for name [SAMBATEST]
[2009/04/20 12:51:10,  5] smbd/statcache.c:stat_cache_add(138)
  stat_cache_add: Added entry 

Re: [Samba] 3.3.3 blocks writing of files ~1.55GB or greater from Windows XP

2009-04-19 Thread Volker Lendecke
On Sat, Apr 18, 2009 at 10:35:14PM -0500, Nikkos Svoboda wrote:
Samba is hosted on a server running Debian-Lenny, on a Reiserfs
 partition.
 
   After upgrading to 3.3.3, Windows XP clients fail to copy files
 through explorer using SMB shares when the file size is around 1.55GB or
 greater in size. The error is Cannot copy Filename.ext: The specified
 network name is no longer available. Copying existing files located on
 the share to the same or any other share fails with the same error.
 Copying files from the share to the local client filesystem works
 correctly. Linux and Mac clients have no problems. I have not tested
 Vista at this point.
 
   The error occurs before any copying begins. The target folder on the
 share will contain a correctly-named, 0 byte file after the attempt to
 write is made. The POSIX permissions of the 0-byte file on the server
 side are correct and the file is owned by the correct user : group.
 
   I do not believe this is related to the error dealing with the
 rotation between ports 139 and 445. The copy does not fail after some
 time, it is immediate. To be sure, I have tried setting both 445 and 139
 alone as the option smb ports = .
 
   Is anyone else seeing this behavior?

Can we see a debug level 10 log of smbd of this problem?

Thanks,

Volker


pgpmpUFD3MXdf.pgp
Description: PGP signature
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] 3.3.3 blocks writing of files ~1.55GB or greater from Windows XP

2009-04-18 Thread Nikkos Svoboda
   Samba is hosted on a server running Debian-Lenny, on a Reiserfs
partition.

  After upgrading to 3.3.3, Windows XP clients fail to copy files
through explorer using SMB shares when the file size is around 1.55GB or
greater in size. The error is Cannot copy Filename.ext: The specified
network name is no longer available. Copying existing files located on
the share to the same or any other share fails with the same error.
Copying files from the share to the local client filesystem works
correctly. Linux and Mac clients have no problems. I have not tested
Vista at this point.

  The error occurs before any copying begins. The target folder on the
share will contain a correctly-named, 0 byte file after the attempt to
write is made. The POSIX permissions of the 0-byte file on the server
side are correct and the file is owned by the correct user : group.

  I do not believe this is related to the error dealing with the
rotation between ports 139 and 445. The copy does not fail after some
time, it is immediate. To be sure, I have tried setting both 445 and 139
alone as the option smb ports = .

  Is anyone else seeing this behavior?
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba