Amdump issues: Difference between revisions
Jump to navigation
Jump to search
Paul.bijnens (talk | contribs) No edit summary |
Paul.bijnens (talk | contribs) No edit summary |
||
| Line 15: | Line 15: | ||
[[ Amdump: /sbin/dump returned 1 ]] | [[ Amdump: /sbin/dump returned 1 ]] | ||
[[ Amdump: mesg read: Connection reset by peer ]] | |||
:This can also trigger error message: sendbackup: "index tee cannot write" | |||
[[ Why does 'amdump' not dump to the holding disk?]] | [[ Why does 'amdump' not dump to the holding disk?]] | ||
| Line 21: | Line 24: | ||
[[Why does 'amdump fail to create level 0 dump']] | [[Why does 'amdump fail to create level 0 dump']] | ||
[[Amdump is terribly slow]] | [[Amdump is terribly slow]] | ||
Revision as of 12:25, 22 March 2006
If you have any problem with amdump first make sure that the command amcheck still succeeds. The amcheck command also points you to a much more detailed and to the point problem area than e.g. the amdump error "all disks failed"
Here is list of issues that amdump may encounter:
Amdump: dumps way too big, must skip incremental dumps
Amdump: infofile update failed
Amdump: cannot overwrite active tape
Amdump: mesg read: Connection reset by peer
- This can also trigger error message: sendbackup: "index tee cannot write"
Why does 'amdump' not dump to the holding disk?
Why does 'amdump' give me 'Tape I/O error'?
Why does 'amdump fail to create level 0 dump'
Issues with other Amanda programs: see Troubleshooting