Tape Input-Output error: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(man links) |
||
| Line 2: | Line 2: | ||
=Problem= | =Problem= | ||
{{man|8|amdump}} and {{man|8|amflush}} give "Input/output error" messages, such as. | |||
taper: tape weekly-002 kb 0 fm 0 writing filemark: Input/output error | taper: tape weekly-002 kb 0 fm 0 writing filemark: Input/output error | ||
=Solution= | =Solution= | ||
{{man|8|amdump}} ''guesses'' how large a dump will be. This can change on a system in constant use (good time to perform remote dumps is durring scheduled downtime). So the major problem is that amdump will figure out what it has room for durring the dump, and if the actual size exceeds the estimate and overflows the tape, you'll see this error. | |||
This error may also occur when the tape drive begins to fail; see [[How To:Diagnose a Failing Tape Drive]]. | This error may also occur when the tape drive begins to fail; see [[How To:Diagnose a Failing Tape Drive]]. | ||
Revision as of 23:14, 30 June 2008
This article is a part of the Troubleshooting collection.
Problem
amdump(8) and amflush(8) give "Input/output error" messages, such as.
taper: tape weekly-002 kb 0 fm 0 writing filemark: Input/output error
Solution
amdump(8) guesses how large a dump will be. This can change on a system in constant use (good time to perform remote dumps is durring scheduled downtime). So the major problem is that amdump will figure out what it has room for durring the dump, and if the actual size exceeds the estimate and overflows the tape, you'll see this error.
This error may also occur when the tape drive begins to fail; see How To:Diagnose a Failing Tape Drive.