Le Mercredi, 27 ao=FBt 2003, =E0 12:34 America/Montreal, Steve Waltner a=20=
> Samba 3.0 had (maybe has) a bug with parsing command line arguments to=20=
> Bug 206 in the Samba Bugzilla database has a patch that fixes=20
> supposedly fixes the problem. It also might have been brought into one=20=
> of the later beta releases of Samba 3.0, which is currently at 3.0rc1.=20=
> You can also resolve this problem by going back to Samba 2.2.8a.
To paraphrase a famous AOL TV ad: "There's never been a better time to=20=
switch to rsync!" More seriously, I only had one Windows PC being=20
backuped with SMB, so I gave rsync a try. The incremental backup speed=20=
went from 0.3 MB/s with SMB to 2.5 MB/s with rsync. 8)
I haven't try a full backup yet, but I hope to get a similar gain.
Logidac Tech., Beaumont, Qu=E9bec, Canada - http://logidac.com/
PGP Key and more: http://guillaume.filion.org/
Jonas Jasas writes:
> I am using Debian linux, samba 3.0.0beta2, backuppc 2.0.0. All
> backups using tar method is ok. With smb method I can do just
> full backup. After full backup when I do incremental backup I
> am getting:
smbclient in samba 3.0.0beta2 doesn't handle the "N" (incremental)
option correctly. I just tried the latest samba 3.0.0rc2 release
and the bug you found has been fixed.
However, 3.0.0rc2 still has several bugs related to long (>=100 byte)
paths. I submitted a patch for one of these bugs, plus added two more
bug reports with patches. So if you apply these three patches to samba
3.0.0rc2 you should be ok:
Get latest updates about Open Source Projects, Conferences and News.