On Fri, Feb 01, 2002 at 12:24:50PM +0100, Thomas Beer wrote: > Hi, > > I added yesterday this to my disklist. > Can anyone explain what the problem is? > > Thanks Tom
Not really a problem. You're backing up the /usr/adm files using amanda. That's where amanda keeps its temporary files. Tar noted that /usr/adm/amanda/daily/index/daemon.system/_share_prog_os/20020201_1.gz.tmp was new enough to need backing up. Then when it went to look for the file, it wasn't there. It's telling you that. That's OK, you probably didn't want to back up the file anyway. The underlying problem is that it is difficult to make a complete backup of a live and changing filesystem. Nothing new about that. In the Bad Old Days we simply shut systems down into single user mode once a day to back them up. Now, we read our backup reports to note anything irregular, dismissing reports of lost tmp files, mail spool files the backup manager couldn't get. If I saw something like ... STRANGE ... ... ?gtar: ./my/boss/home/directory/important/file: Warning: Cannot stat: ... i/o error ... ... Then I might be concerned. > > FAILED AND STRANGE DUMP DETAILS: > > /-- milestone. /usr/adm lev 0 STRANGE > sendbackup: start [milestone.system:/usr/adm level 0] > sendbackup: info BACKUP=/bin/tar > sendbackup: info RECOVER_CMD=/bin/tar -f... - > sendbackup: info end > ? gtar: ./amanda/daily/index/daemon.system/_share_prog_os/20020201_1.gz.tmp: > Warning: Cannot stat: No such file or directory > | Total bytes written: 6461440 (6.2MB, 631kB/s) > sendbackup: size 6310 > sendbackup: end > \-------- > > -- ----------------------------------------------------------------- Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549 URL http://embedded.linuxjournal.com/ -----------------------------------------------------------------
