Some tars are returning with an error (sort of).
---
? gtar: ./dsmith/.xsession-errors: file changed as we read it
| Total bytes written: 163194880
? gtar: Error exit delayed from previous errors
sendbackup: error [/opt/gnome/bin/gtar returned 2]
---
Also:
? gtar: ./net/freeware: Cannot savedir: Permission denied
? gtar: ./net/rmsa: Cannot savedir: Permission denied
? gtar: ./net/user06: Cannot savedir: Permission denied
? gtar: ./net/user5: Cannot savedir: Permission denied
? gtar: ./net/freeware: Warning: Cannot savedir: Permission denied
? gtar: ./net/rmsa: Warning: Cannot savedir: Permission denied
? gtar: ./net/user06: Warning: Cannot savedir: Permission denied
? gtar: ./net/user5: Warning: Cannot savedir: Permission denied
| Total bytes written: 28160000 (27MB, 72kB/s)
? gtar: Error exit delayed from previous errors
sendbackup: error [/tmpbin/tar returned 2]
---
As far as I'm concerned, a tar exit code of 2 can be ignored at this
point.
I have been unsuccessful in ignoring files so far. For the above file
(./dsmith/.xsession-errors) I have tried the following:
./dsmith/.xsession-errors
/net/usercd/dsmith/.xsession-errors
Neither are working.
It appears the other errors are automount problems.
Either way, so far I would like to ignore tar error return code 2 and
continue with the back up.
Does amanda abort the backup of that filesystem entirely with that error
(or any error), or does it backup what it can? Meaning, everytime that
error happens, does amanda say "I give up" and skip to the next and not
even back it up? It says FAILED in the log. If so, then that one file
system (/net/usercd) has never been backed up yet.
thanks
lance
