On Sunday, September 19, 2010 06:30:06 pm Dustin J. Mitchell did opine:

> On Sun, Sep 19, 2010 at 5:32 AM, Gene Heskett <[email protected]> 
wrote:
> > One thing that catches my eye, in the taper.log, it is searching for:
> >  [ama...@coyote Daily]$ cat taper.20100919052724.debug
> > Sun Sep 19 05:27:24 2010: taper: pid 5083 ruid 501 euid 501 version
> > 3.2.0alpha.svn.3416: start at Sun Sep 19 05:27:24 2010 Sun Sep 19
> > 05:27:24 2010: taper: pid 5083 ruid 501 euid 501 version
> > 3.2.0alpha.svn.3416: rename at Sun Sep 19 05:27:24 2010 Sun Sep 19
> > 05:27:24 2010: taper: Amanda::Taper::Scan::traditional stage 1:
> > search for oldest reusable volume Sun Sep 19 05:27:24 2010: taper:
> > Amanda::Taper::Scan::traditional oldest reusable volume is
> > 'Dailys-21' Sun Sep 19 05:27:24 2010: taper:
> > Amanda::Taper::Scan::traditional stage 1: searching oldest reusable
> > volume 'Dailys-21' Sun Sep 19 05:27:24 2010: taper:
> > Amanda::Taper::Scan::traditional result: 'Dailys-21' on
> > file:/amandatapes/Dailys/drive0 slot 21, mode 2 Sun Sep 19 05:27:24
> > 2010: taper: pid 5083 finish time Sun Sep 19 05:27:24 2010
> > [ama...@coyote Daily]$
> > 
> > Where is that spurious '/drive0' coming from in the file:string?
> 
> False alarm - that's how the new changer works, and also explains why
> you were not seeing the data/ link updated.

I see.  Then it must have been on the 8/29 day shift when I changed the 
chg-disk in my amanda.conf, because those files are dated 8/29 roughly 
coincident with the shortly after midnight run time.
 
> So the driver didn't even *try* to write anything to tape in the run
> for which you just pasted a debug log.  Any idea why?
> 
> Dustin

Your guess is as good as mine, there simply isn't anything to indicate the 
failure, or a hint of a reason in the logs I've grepped.  All I know at 
this point is that I have to back up to about svn3341 just to get amflush to 
work.  The current 3419? taps the drive, once for a read that may be the 
tape header file, and once about 2 seconds later for a very quick write 
which might be the status file, then exits silently in another second or so 
even when amflush is run with the -f option.

I think it might help if taper was made a lot more chatty.  Is there a 
debug level option I could pass to it?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
When it comes to helping you, some people stop at nothing.

Reply via email to