On Wed, Oct 6, 2010 at 10:10 AM, Jon LaBadie <j...@jgcomp.com> wrote: > Again, if trying from the server, might this be yet another > tar version incompatibilities?
This is unlikely, but worth checking out all the same - can the version of tar that amrecover is using successfully extract the amfetchdump'd tarfiles? If so, can you "wrap" that tar in a shell script so that it also writes the datastream to a permanent file, and then compare the known-good and known-bad datastreams to see what's going on? Your hypothesis about a difference in offsets makes sense, but maybe there's just random corrupt data in there. It would be good to know at what offset the corruption begins. Dustin -- Open Source Storage Engineer http://www.zmanda.com
