Hello...

On Wed, 2010-02-24 at 17:33 -0600, Dustin J. Mitchell wrote:
> 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.
> 

yea!

> > 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 /.
> 

Was it always that way?  I haven't used amrestore since amfetchdump came
out.


> 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.


I'll spend some time tracking down exactly what is not being stripped
out.  Maybe stderr is being included?  My C programing skills are weak,
so I might not be able to provide a patch, but I can do the legwork to
find out exactly where the problem data is.  Currently my amdump runs
last 19 to 23 hours.  I got a third tape drive for the jukebox
specifically to be able to do restores without killing the running
amdump.  So being able to run amrestore without a workaround would be
good (amfetchdump --yes-I-know-what-I-am-doing --ignore-running-amdump
--use-drive /dev/nst2  would be better :).  In the example I gave the
data was only 25G, but the same workaround would be "interesting" with a
-gt 1Tb restore.


> Dustin
> 


-- 
Christopher McCrory
 "The guy that keeps the servers running"
 
[email protected]
 http://www.pricegrabber.com
 
Let's face it, there's no Hollow Earth, no robots, and
no 'mute rays.' And even if there were, waxed paper is
no defense.  I tried it.  Only tinfoil works.


Reply via email to