samba - Nov 2003 - Still trying to backup 66 GB from LINUX to W2K ***

Hi Everyone.

I'm still having that problem that my samba cannot backup more
than 2 GB onto a Windows share (on a Win2K box) (see messages
earlier in this forum - I have to backup a 66 GB file out of database).

Setting loglevel of SAMBA to "2" I received the following (for the
time running the backup up to the broken connection):

......
[2003/11/18 11:39:47, 3] smbd/server.c:exit_server(495)
  Server exit (normal exit)
[2003/11/18 11:43:08, 0] client/smbmount.c:send_fs_socket(383)
  mount.smbfs: entering daemon mode for service \\ntsrvsr3\cmdhp5, pid=161
[2003/11/18 11:55:12, 3] param/loadparm.c:init_globals(1271)
  Initialising global parameters
[2003/11/18 11:55:12, 3] param/params.c:pm_process(577)
  params.c:pm_process() - Processing configuration file
"/etc/samba/smb.conf"
[2003/11/18 11:55:12, 3] param/loadparm.c:do_section(3055)
  Processing section "[global]"
[2003/11/18 11:55:12, 1] lib/debug.c:debug_message(258)
  INFO: Debug class all level = 2   (pid 32554 from pid 32554)
[2003/11/18 11:55:12, 2] param/loadparm.c:do_section(3073)
  Processing section "[printers]"
[2003/11/18 11:55:12, 2] param/loadparm.c:do_section(3073)
  Processing section "[print$]"
[2003/11/18 11:55:12, 2] param/loadparm.c:do_section(3073)
  Processing section "[bak]"
[2003/11/18 11:55:12, 0] printing/print_cups.c:cups_printer_fn(110)
  Unable to connect to CUPS server localhost - Connection refused
[2003/11/18 12:21:01, 2] client/smbmount.c:send_fs_socket(393)
  mount.smbfs[161]: got signal, getting new socket
[2003/11/18 12:21:11, 2] lib/util_sock.c:open_socket_out(874)
  error connecting to 20.20.20.1:139 (No route to host)
[2003/11/18 12:21:11, 1] libsmb/cliconnect.c:cli_connect(782)
  Error connecting to 20.20.20.1 (No route to host)
[2003/11/18 12:21:11, 0] client/smbmount.c:do_connection(150)
  161: Connection to ntsrvsr3 failed
[2003/11/18 12:21:59, 2] client/smbmount.c:send_fs_socket(393)
  mount.smbfs[161]: got signal, getting new socket
[2003/11/18 12:41:54, 2] client/smbmount.c:send_fs_socket(393)
  mount.smbfs[161]: got signal, getting new socket
[2003/11/18 12:41:54, 2] lib/util_sock.c:open_socket_out(874)
  error connecting to 20.20.20.1:139 (No route to host)
[2003/11/18 12:41:54, 1] libsmb/cliconnect.c:cli_connect(782)
  Error connecting to 20.20.20.1 (No route to host)
[2003/11/18 12:41:54, 0] client/smbmount.c:do_connection(150)
  161: Connection to ntsrvsr3 failed
[2003/11/18 12:42:24, 2] client/smbmount.c:send_fs_socket(393)
  mount.smbfs[161]: got signal, getting new socket
.....

Here are some answers to questions that popped up during the
postings in this forum:

Q: Can you change your backup box from W2K to Linux
A: No I cannot due to company's policies and given situation.
And even if I could, this would not solve the problem.

Q: Did you try NFS instead of SAMBA
A: Yes I did. Same problem.

Q: Does the problem exist if you try to squeeze the file from
W2K out of the linux box directly (making a mount on Linux,
that Windows can access)
A: No. They works! But: It does not solve my problem, because
I cannot put a 66 GB backup file on to the harddrive of the linux
box - there is not enough space left

Q: Do you use EXT3 as filesystem?
A: Yes I do. And the problem exists also on EXT2, REISERFS ....

Q: Did you try to make a new kernel?
A: Yes. It did not make any change. I'm still using 2.4.19 kernel
(SUSE Linux Enterprise Server 8). I tried REDHAT and SUSE 8.2
and MANDRAKE 8.1 on different boxes at home as well - no
change.

Q: Did you try SAMBA 3.0.1?
A: Yes. On a different Linux box I compiled SAMBA 3.0.1pre
from scratch. It did not make any change.

Q: Did you contact SAPDB (manufacturer of the database)? Do
they have a limitation in the database?
A: Yes, I made a ticket at SAP for that. There is no limitation
insided the code of the database. I can sign for that, because the
Windows-release of SAPDB can backup endless Gigabytes to the
same share on the W2K box. I'm still having a ticket at SAP to
tell me which mechanism they use for the backup (TAR, STAR).
---

Any more questions or ideas, guys?!
I'm *now* frustrated and thinking of switching the box with
the SAP system back to Windows..... (that is in fact not a
solution, too)


Kind Regards,
Carsten L?ffler
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



______________________________________________________________________
 This message is intended for the addressee or its representative only.
  Any form of unauthorized use, publication, reproduction, copying or
  disclosure of the content of this e-mail is not permitted. If you are not
  the intended recipient of this e-mail message and its contents, please
  notify the sender immediately and delete this message and all its
  attachments subsequently.

  command ag

Hello, Carsten.Loeffler@command.de,

Mittwoch, 19. November 2003, 17:09 you wrote:

CLcd> [2003/11/18 12:41:54, 1] libsmb/cliconnect.c:cli_connect(782)
CLcd>   Error connecting to 20.20.20.1 (No route to host)
CLcd> [2003/11/18 12:41:54, 0] client/smbmount.c:do_connection(150)
CLcd>   161: Connection to ntsrvsr3 failed

This points to somewhat fundamental issues:

Your TCP/IP-setup seems to be broken.

Samba says

CLcd>   error connecting to 20.20.20.1:139 (No route to host)

What is the 20.20.20.1? The box called ntsrvsr3?
Can you ping it?
What is the ifconfig of your linux-box?

And by the way: What IP is 20.20.20.1?
This seems strange to me.
How did you choose that setting?

Use C-class-adresses like 192.168.0.x for your LAN.

This all is not Samba-stuff ... basic TCP/IP-setup.

CLcd> Any more questions or ideas, guys?!
CLcd> I'm *now* frustrated and thinking of switching the box with
CLcd> the SAP system back to Windows..... (that is in fact not a
CLcd> solution, too)

Check your network-setup first.

-- 
best regards,
Stefan G. Weichinger
mailto:monitor@oops.co.at

Hello, Carsten.Loeffler@command.de,

Mittwoch, 19. November 2003, 17:09 you wrote:

CLcd> Hi Everyone.

CLcd> I'm still having that problem that my samba cannot backup more
CLcd> than 2 GB onto a Windows share (on a Win2K box) (see messages
CLcd> earlier in this forum - I have to backup a 66 GB file out of database).

On the other hand, David Morel has sent me this:
> for the last time, the 2Gb limitation is a problem with smbfs in 2.4
> kernels (which smbmount uses). To circumvent it, either find urban 
> widmark's patches or use cifs with a 2.6 kernel.
> 
> D.Morel
I have not noticed that facts in my setup.

-- 
best regards,
Stefan G. Weichinger
mailto:monitor@oops.co.at

Hi Everyone.

So far: thanks to everyone for the support. I was offline for 2 days,
but tonight I've spent again some time at home on that problem.

My configuration at home is slightly different: I'm using WinXP Pro
instead of W2K Server and I'm using Suse 8.2 instead if Suse
Enterprise Server 8. Kernel release is 2.4.20, Samba is 3.0.1 pre.

To verify that this is not just a simple tar or whatever problem
tonight from my Linux box I made a "dd" and tried to create
a file larger than 4 gb on my Windows box.

And again I've received "File size limit exceeded"
At that byte-count: 2.147.483.647 Bytes. BUT: there's nothing in
the samba actionlog. I only found a message about mounting the
share.

By the way: I'm still using NTFS; nothing else.

Thanks for your advices to try smbtar or rexec. It won't help me.
Because my database only supports to start a backup -- I only can
tell it where to backup to and when (timely); and that's it. I cannot
split or something like that unfortunately.

Thanks again.

_________________________________
Carsten L?ffler
Email: carsten.loeffler@t-online.de