Re: [Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
sounds like you need to clean your tape drive and quite possibly get new tapes. how old are the tapes you're using? they're only good for so many passes. --On December 14, 2007 4:12:29 PM -0500 Lawrence McMahon <[EMAIL PROTECTED]> wrote: Michael; I should also have included that when I did the amverify, I got the following in /var/adm/messages: Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:39:13 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x80 (), ASCQ: 0x1, FRU: 0x0 Dec 14 13:39:14 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:39:14 apocalypse.acsu.buffalo.edu Periodic head cleaning required Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:41:36 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:43:09 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:45:56 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:47:21 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:50:03 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:50:03 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:50:03 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:50:03 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:50:0
Re: [Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
Lawrence McMahon wrote: FAILED AND STRANGE DUMP DETAILS: /-- ubcard.car /opt lev 1 STRANGE sendbackup: start [ubcard.card.buffalo.edu:/opt level 1] sendbackup: info BACKUP=/usr/sbin/ufsdump sendbackup: info RECOVER_CMD=/usr/sbin/ufsrestore -f... - sendbackup: info end ? Unable to create temporary directory in any of the directories listed below: ? /tmp/ ? /var/tmp/ ? / ? Please correct this problem and rerun the program. Yes do that. Or your disk is 100% full, or you the disk became readonly due to a filesystem failure, or equally real bad events.
Re: [Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
Lawrence McMahon wrote: Michael; I should also have included that when I did the amverify, I got the following in /var/adm/messages: Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:39:13 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial I'm not sure what you need more to come to the conclusion that you have a broken disk (or a bad scsi cable?).
Re: amreport analysis
Dustin J. Mitchell wrote:
On Dec 14, 2007 11:11 AM, Tom Herrera <[EMAIL PROTECTED]> wrote:
? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
These are a problem. You should add an exclude for /mnt to your DLE:
brain.milw / {
WHATEVER_DUMPTYPE_YOU_HAD
exclude list append "./mnt"
} -1 le0
| gtar: ./lib/dev-state/gpmctl: socket ignored
| gtar: ./lib/dev-state/log: socket ignored
| gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
| gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored
These are harmless, but you can exclude them, too, if you'd like.
Minor correction: they are harmless indeed, but you do not need
to exclude them, because Amanda expects that output, and classifies
it as "normal". You will not see these "normal" lines in the report
unless there are also "error" or "strange" lines.
Each output line of the dumpprogram (gtar above) is classified
as "normal" All the other lines are flagged with a question mark.
When the return code of gtar indicates success, but contains
unexpected lines, Amanda flags the dump as strange, but still puts
in on tape. Amanda leaves it up to you to interpret the strange
lines, and see if they are harmful or not.
When the return code of gtar indicates a failure, those non-normal
output lines are probably the cause of the error.
When informing you about "strange" or "error" in the report, Amanda
always shows the complete output, including the "normal" lines, to
allow you to interpret those lines in the context.
Re: [Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
Michael; I should also have included that when I did the amverify, I got the following in /var/adm/messages: Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:39:13 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:39:13 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x80 (), ASCQ: 0x1, FRU: 0x0 Dec 14 13:39:14 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:39:14 apocalypse.acsu.buffalo.edu Periodic head cleaning required Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:41:36 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:41:36 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:43:09 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:43:09 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:45:56 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:45:56 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:47:21 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUMSerial Number: U $ Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Sense Key: Media Error Dec 14 13:47:21 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0 Dec 14 13:50:03 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.warning] WARNI NG: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0 (st12): Dec 14 13:50:03 apocalypse.acsu.buffalo.edu Error for Command: read Error Level: Fatal Dec 14 13:50:03 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Requested Block: 12495 Error Block: 12495 Dec 14 13:50:03 apocalypse.acsu.buffalo.edu scsi: [ID 107833 kern.notice] Vendor: QUANTUM
Re: [Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
Sorry about that, see below.
However, I was concerned about the errors like:
** Error detected ()
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
FAILED AND STRANGE DUMP DETAILS:
/-- ubcard.car /opt lev 1 STRANGE
sendbackup: start [ubcard.card.buffalo.edu:/opt level 1]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/sbin/ufsrestore -f... -
sendbackup: info end
? Unable to create temporary directory in any of the directories listed below:
? /tmp/
? /var/tmp/
? /
? Please correct this problem and rerun the program.
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Fri Dec 14 00:44:51 2007
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rdsk/c0t0d0s0 (ubcard.card.buffalo.edu:/) to standard
output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 157332 blocks (76.82MB) on 0.00 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
| DUMP: 157310 blocks (76.81MB) on 1 volume at 3068 KB/sec
| DUMP: DUMP IS DONE
sendbackup: size 78655
sendbackup: end
\
/-- igor.cc.bu /usr lev 1 STRANGE
sendbackup: start [igor.cc.buffalo.edu:/usr level 1]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/sbin/ufsrestore -f... -
sendbackup: info end
? Unable to create temporary directory in any of the directories listed below:
? /tmp/
? /var/tmp/
? /
? Please correct this problem and rerun the program.
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Fri Dec 14 00:31:11 2007
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rdsk/c0t1d0s0 (igor.cc.buffalo.edu:/) to standard output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 7807840 blocks (3812.42MB) on 0.06 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
| DUMP: 46.43% done, finished in 0:11
| DUMP: 90.44% done, finished in 0:02
| DUMP: 7749374 blocks (3783.87MB) on 1 volume at 2983 KB/sec
| DUMP: DUMP IS DONE
sendbackup: size 3874687
sendbackup: end
\
thanks,
Larry
Michael Loftis wrote:
--On December 14, 2007 2:15:29 PM -0500 Lawrence McMahon
<[EMAIL PROTECTED]> wrote:
Hi;
Our daily report of this tape came out ok, but when I did an
amverify,
I got the attached.
Does this seem like a tape problem, or tape drive problem?
There should be a section detailing what was STRANGE about the verify,
and you seem to have failed to include that If that's indeed the
whole output then I'm at a loss.
These dumps were to tape DRD021.
The next tape Amanda expects to use is: DRD022.
FAILURE AND STRANGE DUMP SUMMARY:
ubcard.car /opt lev 1 STRANGE
igor.cc.bu /usr lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:11
Run Time (hrs:min) 4:51
Dump Time (hrs:min)9:12 4:07 5:05
Output Size (meg) 63639.939047.424592.4
Original Size (meg) 63639.939047.424592.4
Avg Compressed Size (%) -- -- --(level:#disks
...)
Filesystems Dumped 279 26253 (1:192 2:40 3:18
4:3)
Avg Dump Rate (k/s) 1968.5 2700.1 1376.3
Tape Time (hrs:min)3:48 2:14 1:34
Tape Size (meg) 62769.438177.024592.4
Tape Used (%) 93.7 57.0 36.7 (level:#disks
...)
Filesystems Taped 279 26253 (1:192 2:40 3:18
4:3)
Avg Tp Write Rate (k/s) 4708.1 4873.7 4472.3
USAGE BY TAPE:
LabelTime Size %Nb
DRD021 3:48 62769.4 93.7 279
--
"Genius might be described as a supreme capacity for getting its
possessors
into trouble of all kinds."
-- Samuel Butler
Re: [Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
--On December 14, 2007 2:15:29 PM -0500 Lawrence McMahon
<[EMAIL PROTECTED]> wrote:
Hi;
Our daily report of this tape came out ok, but when I did an amverify,
I got the attached.
Does this seem like a tape problem, or tape drive problem?
There should be a section detailing what was STRANGE about the verify, and
you seem to have failed to include that If that's indeed the whole
output then I'm at a loss.
These dumps were to tape DRD021.
The next tape Amanda expects to use is: DRD022.
FAILURE AND STRANGE DUMP SUMMARY:
ubcard.car /opt lev 1 STRANGE
igor.cc.bu /usr lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:11
Run Time (hrs:min) 4:51
Dump Time (hrs:min)9:12 4:07 5:05
Output Size (meg) 63639.939047.424592.4
Original Size (meg) 63639.939047.424592.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 279 26253 (1:192 2:40 3:18
4:3)
Avg Dump Rate (k/s) 1968.5 2700.1 1376.3
Tape Time (hrs:min)3:48 2:14 1:34
Tape Size (meg) 62769.438177.024592.4
Tape Used (%) 93.7 57.0 36.7 (level:#disks ...)
Filesystems Taped 279 26253 (1:192 2:40 3:18
4:3)
Avg Tp Write Rate (k/s) 4708.1 4873.7 4472.3
USAGE BY TAPE:
LabelTime Size %Nb
DRD021 3:48 62769.4 93.7 279
--
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
[Fwd: UB DRD AMANDA VERIFY REPORT FOR DRD021]
Hi;
Our daily report of this tape came out ok, but when I did an
amverify, I got the attached.
Does this seem like a tape problem, or tape drive problem?
These dumps were to tape DRD021.
The next tape Amanda expects to use is: DRD022.
FAILURE AND STRANGE DUMP SUMMARY:
ubcard.car /opt lev 1 STRANGE
igor.cc.bu /usr lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:11
Run Time (hrs:min) 4:51
Dump Time (hrs:min)9:12 4:07 5:05
Output Size (meg) 63639.939047.424592.4
Original Size (meg) 63639.939047.424592.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 279 26253 (1:192 2:40 3:18 4:3)
Avg Dump Rate (k/s) 1968.5 2700.1 1376.3
Tape Time (hrs:min)3:48 2:14 1:34
Tape Size (meg) 62769.438177.024592.4
Tape Used (%) 93.7 57.0 36.7 (level:#disks ...)
Filesystems Taped 279 26253 (1:192 2:40 3:18 4:3)
Avg Tp Write Rate (k/s) 4708.1 4873.7 4472.3
USAGE BY TAPE:
LabelTime Size %Nb
DRD021 3:48 62769.4 93.7 279
--- Begin Message ---
Tapes: DRD021
Errors found:
DRD021 ():
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
DRD021 ():
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
DRD021 ():
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
DRD021 ():
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
DRD021 ():
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
DRD021 ():
amrestore: error reading file header: I/O error
** No header
0+0 in
0+0 out
amverify dlt-daily
Fri Dec 14 10:17:48 EST 2007
Using device /dev/rmt/0ubn
Volume DRD021, Date 20071214
Skipped workflow-test-db.acsu.buffalo.edu._.20071214.2 (** Cannot do /sbin/dump
dumps)
Skipped redhat1.buffalo.edu._usr.20071214.2 (** Cannot do /sbin/dump dumps)
Skipped console.acsu.buffalo.edu._home.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped idb2.acsu.buffalo.edu._opt.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idbdev2.acsu.buffalo.edu._opt.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idb1.acsu.buffalo.edu._opt.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped bishop.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped iprint-01.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped download1.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped download2.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped idbdev1.acsu.buffalo.edu._opt.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped sysman2.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped sysman1.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped consol4.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped console-c.acsu.buffalo.edu._home.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped console-f.acsu.buffalo.edu._.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped consol2.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped iprint-02.acsu.buffalo.edu._usr.20071214.1 (** Cannot do /sbin/dump
dumps)
Checked win-dfsgw-9.acsu.buffalo.edu._.20071214.1
Skipped consol3.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Checked inpmon02.dce.buffalo.edu._opt.20071214.1
Checked dfsgw2.acsu.buffalo.edu._.20071214.1
Checked kerb1.acsu.buffalo.edu._.20071214.1
Checked gory.acsu.buffalo.edu._opt.20071214.1
Checked heqet-hw.dce.buffalo.edu._.20071214.1
Skipped idb2.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idb1.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped redhat1.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped console.acsu.buffalo.edu._.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idbdev2.acsu.buffalo.edu._usr.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idbdev1.acsu.buffalo.edu._usr.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped workflow-test-db.acsu.buffalo.edu._opt.20071214.1 (** Cannot do
/sbin/dump dumps)
Skipped console-c.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped sysman1.acsu.buffalo.edu._var.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idb2.acsu.buffalo.edu._usr.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped idbdev1.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped idbdev2.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped console.acsu.buffalo.edu._boot.20071214.1 (** Cannot do /sbin/dump
dumps)
Skipped console-c.acsu.buffalo.edu._.20071214.1 (** Cannot do /sbin/dump dumps)
Skipped consol2
Re: amreport analysis
On Fri, Dec 14, 2007 at 08:11:14AM -0800, Tom Herrera wrote: > > Quick thanks to Jon, Gene, Chris, and John for assist with my amflush > question > > Am now looking for folks suggestions on whay I'm seeing on my amreport. > I've copied it below. Since I'm still very new to both Linux and Amanda I'm > wondering which lines I need to be concerned about and which ones I can > ignore. > > Any assistance would be appreciated. > > These dumps were to tape Daily-004. > The next tape Amanda expects to use is: Daily-005. > > FAILURE AND STRANGE DUMP SUMMARY: > brain.milw / lev 0 FAILED [/bin/gtar returned 2] The "why" is shown below. Tar exits "2" with lots of minor errors during a backup. It exits "1" on real failures, syntax errors etc. BTW on Unix/Linux, exit (aka return) of "0" is the norm, indicating success. > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:06 > Run Time (hrs:min) 3:45 > Dump Time (hrs:min)1:30 1:28 0:02 > Output Size (meg) 10241.210241.00.2 > Original Size (meg) 16661.716658.73.0 > Avg Compressed Size (%)44.4 44.58.4 (level:#disks ...) > Filesystems Dumped 10 7 3 (1:2 2:1) > Avg Dump Rate (k/s) 1943.5 1980.22.6 > > Tape Time (hrs:min)2:21 2:21 0:00 > Tape Size (meg) 10241.610241.20.3 > Tape Used (%) 51.3 51.30.0 (level:#disks ...) > Filesystems Taped10 7 3 (1:2 2:1) > Avg Tp Write Rate (k/s) 1235.6 1239.4 13.3 > > > FAILED AND STRANGE DUMP DETAILS: > > /-- brain.milw / lev 0 FAILED [/bin/gtar returned 2] > sendbackup: start [brain.milw.nvisia.com:/ level 0] > sendbackup: info BACKUP=/bin/gtar > sendbackup: info RECOVER_CMD=/bin/gtar -f... - > sendbackup: info end The lines below have leading either "?" or "|". The "|" would not have caused the "failed and strange" report to print and are just along for the ride because other more serious things are being reported, the ones with the "?". > ? gtar: ./mnt/cdrom: Cannot savedir: Input/output error > ? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error So these are the only problems. Likely no CD was installed. I'd suggest you add an exclude option for /mnt/cdrom. > | gtar: ./lib/dev-state/gpmctl: socket ignored > | gtar: ./lib/dev-state/log: socket ignored > | gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored > | gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored > | gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored > | gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored > | gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored > | gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored > | Total bytes written: 3503226880 (3.3GiB, 1.7MiB/s) > ? gtar: Error exit delayed from previous errors > sendbackup: error [/bin/gtar returned 2] > \ > > > NOTES: Notes are just that, info for you. But one is important. > planner: Preventing bump of brain.milw.nvisia.com:/ as directed. > planner: Last full dump of brain.milw.nvisia.com:/mnt/archive_vol/home on > tape Daily-004 overwritten on this run. This is pretty important. Why don't you have multiple full dumps on tape? > planner: Dump too big for tape: full dump of > brain.milw.nvisia.com:/mnt/archive_vol/home delayed. This is the big one to pay attention to. Amanda backs up entities called Disklist Entries (DLEs) named after the "disklist" file. Until recent versions of amanda, a full dump of each DLE had to be smaller than a single tape; amanda did not split dumps across tapes. The default is still to not split dumps. So for this DLE, a full dump is needed but can't be done because it won't fit. Either get bigger tapes :), make this multiple DLEs using the exclude/include methods, or upgrade amanda and configure for tape spanning. > planner: Full dump of was.demo.nvisia.com:/ promoted from 3 days ahead. > planner: Full dump of was.demo.nvisia.com:/opt promoted from 3 days ahead. > planner: Full dump of brain.milw.nvisia.com:/mnt/archive_vol/utility > promoted from 3 days ahead. > planner: Full dump of > brain.milw.nvisia.com:/mnt/archive_vol/cvs_repository promoted from 3 days > ahead. > planner: Full dump of brain.milw.nvisia.com:/boot promoted from 3 days > ahead. > taper: tape Daily-004 kb 10487360 fm 10 [OK] > > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > brain.milw.n / 0 FAILED --- > brain.milw.n /boot 06592 6624 --0:041537.3 0:051318.2 > brain.milw.n -xport/home 0 5220
Re: amreport analysis
On Dec 14, 2007 11:11 AM, Tom Herrera <[EMAIL PROTECTED]> wrote:
> ? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
> ? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
These are a problem. You should add an exclude for /mnt to your DLE:
brain.milw / {
WHATEVER_DUMPTYPE_YOU_HAD
exclude list append "./mnt"
} -1 le0
> | gtar: ./lib/dev-state/gpmctl: socket ignored
> | gtar: ./lib/dev-state/log: socket ignored
> | gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
> | gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
> | gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
> | gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
> | gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
> | gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored
These are harmless, but you can exclude them, too, if you'd like.
Dustin
--
Storage Software Engineer
http://www.zmanda.com
amreport analysis
Quick thanks to Jon, Gene, Chris, and John for assist with my amflush
question
Am now looking for folks suggestions on whay I'm seeing on my amreport.
I've copied it below. Since I'm still very new to both Linux and Amanda I'm
wondering which lines I need to be concerned about and which ones I can
ignore.
Any assistance would be appreciated.
These dumps were to tape Daily-004.
The next tape Amanda expects to use is: Daily-005.
FAILURE AND STRANGE DUMP SUMMARY:
brain.milw / lev 0 FAILED [/bin/gtar returned 2]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:06
Run Time (hrs:min) 3:45
Dump Time (hrs:min)1:30 1:28 0:02
Output Size (meg) 10241.210241.00.2
Original Size (meg) 16661.716658.73.0
Avg Compressed Size (%)44.4 44.58.4 (level:#disks ...)
Filesystems Dumped 10 7 3 (1:2 2:1)
Avg Dump Rate (k/s) 1943.5 1980.22.6
Tape Time (hrs:min)2:21 2:21 0:00
Tape Size (meg) 10241.610241.20.3
Tape Used (%) 51.3 51.30.0 (level:#disks ...)
Filesystems Taped10 7 3 (1:2 2:1)
Avg Tp Write Rate (k/s) 1235.6 1239.4 13.3
FAILED AND STRANGE DUMP DETAILS:
/-- brain.milw / lev 0 FAILED [/bin/gtar returned 2]
sendbackup: start [brain.milw.nvisia.com:/ level 0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f... -
sendbackup: info end
? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
| gtar: ./lib/dev-state/gpmctl: socket ignored
| gtar: ./lib/dev-state/log: socket ignored
| gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
| gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored
| Total bytes written: 3503226880 (3.3GiB, 1.7MiB/s)
? gtar: Error exit delayed from previous errors
sendbackup: error [/bin/gtar returned 2]
\
NOTES:
planner: Preventing bump of brain.milw.nvisia.com:/ as directed.
planner: Last full dump of brain.milw.nvisia.com:/mnt/archive_vol/home on
tape Daily-004 overwritten on this run.
planner: Dump too big for tape: full dump of
brain.milw.nvisia.com:/mnt/archive_vol/home delayed.
planner: Full dump of was.demo.nvisia.com:/ promoted from 3 days ahead.
planner: Full dump of was.demo.nvisia.com:/opt promoted from 3 days ahead.
planner: Full dump of brain.milw.nvisia.com:/mnt/archive_vol/utility
promoted from 3 days ahead.
planner: Full dump of
brain.milw.nvisia.com:/mnt/archive_vol/cvs_repository promoted from 3 days
ahead.
planner: Full dump of brain.milw.nvisia.com:/boot promoted from 3 days
ahead.
taper: tape Daily-004 kb 10487360 fm 10 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
brain.milw.n / 0 FAILED ---
brain.milw.n /boot 06592 6624 --0:041537.3 0:051318.2
brain.milw.n -xport/home 0 52201925220224 -- 47:261834.2 47:271833.9
brain.milw.n -repository 0 38270 30784 80.4 1:05 470.5 0:241267.5
brain.milw.n -repository 1 450 64 14.2 0:39 0.8 0:02 39.9
brain.milw.n -e_vol/home 22110224 10.6 0:38 5.0 0:02 136.5
brain.milw.n -ol/utility 0 124150 39328 31.7 1:18 505.0 0:301298.6
brain.milw.n /usr2 1 470 64 13.6 0:22 1.4 0:23 2.8
was.demo.nvi / 0 1991870 690112 34.6 4:092775.1 34:37 332.2
was.demo.nvi /home 0 74908303354208 44.8 28:031992.7 43:091295.4
was.demo.nvi /opt0 21866401145728 52.4 6:103093.2 14:491289.2
(brought to you by Amanda version 2.4.3)
--
View this message in context:
http://www.nabble.com/amreport-analysis-tp14338749p14338749.html
Sent from the Amanda - Users mailing list archive at Nabble.com.
