On Thu, Nov 11, 2010 at 08:28:44AM +0100, Titl Erich wrote: > Hi > > I am getting STRANGE reports about every other day from amanda 3.1.3 > > STRANGE DUMP DETAILS: > > /-- amanda.ruf.ch / lev 1 STRANGE > > sendbackup: start [amanda.ruf.ch:/ level 1] > > sendbackup: info BACKUP=/bin/tar > > sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ... > > sendbackup: info end > > ? /bin/tar: > ./etc/amanda/DailySet1/index/srvx-lx01-afa.ruf.group/_usr/20101111010001_1.g > z.tmp: Warning: Cannot stat: No such file or directory > > | Total bytes written: 2754560 (2.7MiB, 3.4MiB/s) > > sendbackup: size 2690 > > sendbackup: end > > \-------- [ snip ] > > It looks like it has a problem with compressing the index. Any ideas? >
No, I do not think it is having a problem. Notice your files are named XYZ".gz.tmp". The ".tmp" indicates it is a temporary file, possibly existing for only a short time. In this case, when the index is completed, the file is renamed without the ".tmp". The message you are receiving arises because of the way tar works. A list of files to be backed up is generated and then the backup is done. On an active directory tree, it is not uncommon for changes to occur between generating the list and actually backing up the specific files in the list. Certainly, the Amanda directory tree is "active" during an amdump run!! So such messages should be expected. Another "strange dump" message you may see is "file changed as we backed it up". jl -- Jon H. LaBadie [email protected] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
