On Sun, Jan 18, 2004 at 08:17:40AM -0600, Fran Fabrizio wrote:
> 
> On all of my Samba-based backups, I am getting STRANGE reports like this:
> 
> /-- keep.cis.u //snapper/dfs/home/faculty lev 0 STRANGE
> sendbackup: start [keep.cis.uab.edu://snapper/dfs/home/faculty level 0]
> sendbackup: info BACKUP=/usr/bin/smbclient
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> ? [2004/01/18 03:56:41, 0] client/clitar.c:process_tar(1433)
> ?   tar: dumped 111876 files and directories
> ? [2004/01/18 03:56:41, 0] client/clitar.c:process_tar(1434)
> |   Total bytes written: 12519055360
> sendbackup: size 12225640
> sendbackup: end
> \--------
> 
> Is there really any problem here?  I can't see one from this output, and 
> the client logs all look fine.  For some reason, it just thinks that the 
> tar output of number of files dumped is strange.  I don't think I've seen 
> this on my non-Samba dumps.  Anyone else see this?

Programs that do backups output many messages.  Lots are "normal".
Amanda tries to keep a catalog of those that should be considered "normal".
If a version of the backup program adds new "normal" messages, or you hit
one that is not cataloged, or changes existing ones (sometimes even an
extra space or a capitalization or punctuation change), amanda will flag
it as "strange".  It is not considered a failed dump because the exit
status of the backup program indicated success.

You may be working with a very recent version of Samba that did indeed
change those two messages but an unpatched version of amanda that adjusted
the "normal" message catalog.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)