Tape Input-Output error: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
m (Tape Input/Output error moved to Tape Input-Output error: rename to avoid slashes)
No edit summary
Line 1: Line 1:
{{Troubleshooting Category|Error Messages}}{{Troubleshooting Category|Amdump}}{{Troubleshooting Category|Amflush}}
{{Troubleshooting Header}}
{{Troubleshooting Problem}}
=Problem=
 
[[amdump]] and [[amflush]] give "Input/output error" messages, such as.  
[[amdump]] and [[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
{{Troubleshooting Solution}}
=Solution=
[[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.  
[[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:23, 22 May 2007

This article is a part of the Troubleshooting collection.

Problem

amdump and amflush give "Input/output error" messages, such as.

  taper: tape weekly-002 kb 0 fm 0 writing filemark: Input/output error

Solution

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.