On Wed, Feb 24, 2010 at 5:08 PM, Christopher <[email protected]> wrote: > amfetchdump does not seem to have this problem, but you cannot run > amfetchdump while amdump is running (which would be a cool feature ;)
We're working on that. In fact, I think it should be doable in 3.1. I'll make a note to test it before the release. > I suspect something in amrestore does not like the 'part X/Y' text. I > looked at the source, but nothing jumped out at me as the cause. Your first case, of amrestore trucking right on after finding the dump it was looking for, is "expected" behavior - amrestore needs to scan the whole tape, in case there are other dumps matching some.server /. Amrestore is really not very good at re-assembling dumps. I suspect amrestore is outputting something to stdout despite the use of -p, which is getting mixed into the datastream. You could try the -p command piped to a file instead of to /bin/restore. Since it looks like restore failed its checksum on the first bytes in the file, I expect a hex editor would show the offending message in the first few bytes of the piped output. Dustin -- Open Source Storage Engineer http://www.zmanda.com
