On Sun, Sep 19, 2010 at 5:32 AM, Gene Heskett <gene.hesk...@gmail.com> 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. 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 -- Open Source Storage Engineer http://www.zmanda.com
