Unexpected field value in snapshot file: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
m (typo)
(reformat, use header template)
Line 1: Line 1:
{{Troubleshooting Problem}}
{{Troubleshooting Header}}
=Problem=

amdump fails with e.g.,
amdump fails with e.g.,
  planner: disk HOSTNAME:/path, estimate of level NNN failed: -1.
  planner: disk HOSTNAME:/path, estimate of level NNN failed: -1.
Line 5: Line 7:
  tar: Unexpected field value in snapshot file
  tar: Unexpected field value in snapshot file
yet the estimate of the level 0 succeeded.
yet the estimate of the level 0 succeeded.
{{Troubleshooting Solution}}
=Solution=
There are two possible causes for this problem.
There are two possible causes for this problem.


Line 16: Line 18:
* http://forums.zmanda.com/archive/index.php/t-299.html
* http://forums.zmanda.com/archive/index.php/t-299.html
* http://savannah.gnu.org/bugs/?18487 (possible source of snapshot corruption)
* http://savannah.gnu.org/bugs/?18487 (possible source of snapshot corruption)
[[Category:Error Messages|{{PAGENAME}}]]
[[Category:Amdump|{{PAGENAME}}]]

Revision as of 23:19, 22 May 2007



This article is a part of the Troubleshooting collection.

Problem

 amdump fails with e.g., 

planner: disk HOSTNAME:/path, estimate of level NNN failed: -1.

and an examination of the relevant sendsize log reveals 

tar: Unexpected field value in snapshot file

yet the estimate of the level 0 succeeded.

Solution

There are two possible causes for this problem.

If you are using a version of Amanda prior to 2.5.0p2 with GNU tar 1.15.91 or later, then this is due to a format change in tar that is not recognized by Amanda. Either upgrade Amanda to 2.5.0p2 or later, or downgrade tar.

This error may also be caused by corrupt tar incremental snapshot files; in this case, removing the suspect file (without the .new suffix) will correct the error.

Links

Retrieved from ‘http://wiki.zmanda.com/index.php?title=Unexpected_field_value_in_snapshot_file&oldid=4630’