Hello, I was wondering if anyone had insight in the matter of trying to backup a large partition while the files on that partition are currently being updated/deleted? We knew we were getting a lot of error messages so we decided to call the reported error messages "normal" by defining the error message string as DMP_NORMAL instead of DMP_STRANGE. Anyhow, please view the following output below:
Backup Account wrote at 05:34 -0600 on Oct 26: > /-- elmer /uv/staging lev 1 FAILED [/local/backup/bin/gtar returned 2] > sendbackup: start [elmer:/uv/staging level 1] > sendbackup: info BACKUP=/local/backup/bin/gtar > sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/local/backup/bin/gtar -f... - > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > | gtar: ./build/work/Release/s2DEN/chroot/tsc/sources/FreeBSD-tsc-4/gnu/usr.bin/cc/doc/CVS/Repository: Warning: Cannot stat: No such file or directory . [snip] . > ? gtar: >./build/work/Release/s2DEN/chroot/tsc/sources/FreeBSD-tsc-4/lib/libcompat/CVS: Cannot savedir: No such file or directory . [snip] . > | Total bytes written: 179609600 (171MB, 136kB/s) > ? gtar: Error exit delayed from previous errors > sendbackup: error [/local/backup/bin/gtar returned 2] > \-------- Note: -->> gtar exited with a non-zero exit code for some reason? We don't know why the tar err'd, but when doing a verify, it was getting called with --ignore-failed-read. So we think it might be either a bug in tar or the error was caused by something else? Also, does anyone know how to not exclude lines in the report even though they are 'NORMAL'. Possibly adding something like DMP_NORMAL_DONT_REPORT to go along with our current DMP_NORMAL and DMP_STRANGE? Any help is appreciated, Eric Nelson AGAIN, THANK YOU FOR TAKING THE TIME TO LOOK AT THIS!!!
