We've been running amanda 242p2 with an Exabyte 220 library for the most
part with good success, but we seem to get a lot of 'not at start of tape'
errors. Looking back at the amverify reports, they seem to be primarily on
smbclient backups. We get frequent strange smbclient dumps due to sharing
violations; could this smbclient error output data be cluttering up the
backup stream? Tapes and drive are all new, and it occurs on several
different tapes, so I'm confident it's not a hardware issue. Any ideas?
Here's an example:
DailySet152 (server.__LEAH5_D$.20010502.1):
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: restoring server.__LEAH5_D$.20010502.1
gzip: stdin: decompression OK, trailing garbage ignored
/bin/gtar: Skipping to next header
/bin/gtar: Error exit delayed from previous errors
64+0 records in
64+0 records out
DailySet152 (server.__LEAH5_C$.20010502.1):
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: restoring server.__LEAH5_C$.20010502.1
gzip: stdin: decompression OK, trailing garbage ignored
/bin/gtar: Skipping to next header
/bin/gtar: Error exit delayed from previous errors
64+0 records in
64+0 records out
thanks,
Carey Jung
IT Freedom
[EMAIL PROTECTED]
512.419.0070, fax 419.0080
