the problem is that smbtar sends some other info at the end, and the size line is not properly parsed in samba. I created patches for Samba 3rc1, rc2 but not for 3.0.0 version.
Please, make noise, bother me, to post a patch. Regards, gregor Intelicom d.o.o. Security software company http://www.intelicom.si email: [EMAIL PROTECTED] tel.: ++386 5 6309 158 fax.: ++386 5 6279 355 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stefan G. Weichinger Sent: Thursday, September 25, 2003 5:58 PM To: [EMAIL PROTECTED] Subject: Amanda and Samba 3.0.0 Hi, amanda-users, has anyone tried using the shiny new Samba 3.0 with Amanda? I compiled Samba 3.0 today and recompiled Amanda 2.4.4p1, too, just to make sure it knows about that new smbclient (donīt know if that was necessary). Now I get some ugly "driver: [no backup size line]" in my amstatus. The sendbackup.xy.debug for such a share looks like: > sendbackup: debug 1 pid 17352 ruid 0 euid 0: start at Thu Sep 25 17:39:31 2003 > /usr/local/libexec/sendbackup: version 2.4.4p1 > parsed request as: program `GNUTAR' > disk `//oops2/Dokeinst' > device `//oops2/Dokeinst' > level 1 > since 2003:9:23:21:11:31 > options `|;auth=bsd;index;exclude-file=.RECYCLER*;' > sendbackup: try_socksize: send buffer size is 65536 > sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50019 > sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50020 > sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50021 > sendbackup: time 0.001: waiting for connect on 50019, then 50020, then 50021 > sendbackup: time 0.010: stream_accept: connection from 192.168.0.10.50027 > sendbackup: time 0.010: stream_accept: connection from 192.168.0.10.50028 > sendbackup: time 0.010: stream_accept: connection from 192.168.0.10.50029 > sendbackup: time 0.010: got all connections > sendbackup-gnutar: time 0.038: doing level 1 dump from date: 2003-09-23 21:11:31 GMT > sendbackup-gnutar: time 0.042: backup of \\oops2\Dokeinst > sendbackup: time 0.053: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" > sendbackup: time 0.043: spawning /usr/bin/smbclient in pipeline > sendbackup: argument list: smbclient \\oops2\Dokeinst -U backup -E -d0 -TXqcg - .RECYCLER* > sendbackup-gnutar: time 0.055: /usr/bin/smbclient: pid 17357 > sendbackup: time 0.381: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \All Users\Anwendungsdaten\* > sendbackup: time 0.453: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \All Users\Dokumente\* > sendbackup: time 0.455: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \All Users\DRM\* > sendbackup: time 4.297: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \LocalService\* > sendbackup: time 4.298: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \NetworkService\* > sendbackup: time 4.299: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \Stefan\* > sendbackup: time 4.301: 124: strange(?): [2003/09/25 17:39:35, 0] client/clitar.c:process_tar(1433) > sendbackup: time 4.301: 124: strange(?): tar: dumped 537 files and directories > sendbackup: time 4.302: 124: strange(?): [2003/09/25 17:39:35, 0] client/clitar.c:process_tar(1434) > sendbackup: time 4.303: 124: strange(?): Total bytes written: 9443840 > sendbackup: time 4.312: index created successfully > sendbackup: time 4.315: error [no backup size line] > sendbackup: time 4.316: pid 17352 finish time Thu Sep 25 17:39:35 2003 The line > sendbackup: argument list: smbclient \\oops2\Dokeinst -U backup -E -d0 -TXqcg - .RECYCLER* seemed odd to me, I checked dumptype and excludes: > define dumptype root-tar { > global > program "GNUTAR" > comment "root partitions dumped with tar" > compress none > exclude ".\Downloads\*" > exclude ".\hiberfil.sys" > exclude ".\RECYCLER\*" > priority low > dumpcycle 4 > } I will have a closer look at the exclude-options of the new smbclient. Maybe leaving the excludes away for testing tells me more. Good old Samba-exclusion-topic ;-) --- I havenīt explored further, but just want to probe: Is there a patch necessary to use Amanda 2.4.4p1 with Samba 3.0? If yes, does that patch exist already ? ;-) Thank you, Stefan G. Weichinger mailto:[EMAIL PROTECTED]