Hello again, On Saturday 14 October 2006 01:33, Michael Brennen wrote: > Hello again Kern, > > Sorry to be a pest, but current CVS as of this morning, after your post, is > still failing the same way it was before.
By the way, I don't consider you to be a pest. There is no problem telling me that a fix that I was hoping would fix the problem does not fix your problem. I'll keep working on it until we get it fixed. Until now, it wasn't the highest priority on my list of things to do ... I should have specified more clearly in previous email that I am having problems distinguishing between two bug reports that you have filed. One is bug #687, which is not very clear to me, but seems to be similar to bug #689. For bug 689, I do know which test you are referring to since you explicitly mention it in the bug report, but I just would like to know if it is the problem you are referring to in this email, or if there is another test/problem. It would be helpful if I could understand which of the two bug reports (or both) that what you write here applies to -- i.e. which of the two bugs are still giving you problems? Is either one fixed? Please add the response to each of the bug reports as a bug note, then it will be clear to me if I can close one of the bugs or work on both of them. Thanks. Regards, Kern > > I have a totally different autochanger in place now to run the regress tests. > It is a two drive unit, a different brand than the previous tests I have run. > I can duplicate with this unit exactly what I was seeing before. These tests > are run against CVS as of this morning. I did a cold rebuild of the regress > tests to be sure and get the new code in place. > > The problem again is that Bacula does the following: > > * loads slot 2 into drive 1 > * unloads slot 1 from drive 0 > * tries to load slot 2 into drive 0 > > The problem is that there is no unload of slot 2 from drive 1 prior to > attempting to load slot 2 into drive 0. I do not see how this can be related > to mtx-changer, as mtx-changer only does what it is told. In this case > mtx-changer was never told to unload slot 2 from drive 1. > > The mtx-changer log segments are below. These are contiguous lines in the > original file; I have interleaved a few comments to try and make it easy to > read. > > -- Michael > > > 20061013-17:32:23 Parms: /dev/sg14 loaded 1 /dev/nst8 0 > 20061013-17:32:23 Doing mtx -f /dev/sg14 0 -- to find what is loaded > 20061013-17:32:34 Parms: /dev/sg14 loaded 0 /dev/nst8 0 > 20061013-17:32:35 Doing mtx -f /dev/sg14 0 -- to find what is loaded > 20061013-17:32:44 Parms: /dev/sg14 loaded 2 /dev/nst9 1 > 20061013-17:32:44 Doing mtx -f /dev/sg14 1 -- to find what is loaded > 20061013-17:32:44 Parms: /dev/sg14 load 2 /dev/nst9 1 > 20061013-17:32:44 Doing mtx -f /dev/sg14 load 2 1 > 20061013-17:33:03 Device /dev/nst9 - not ready, retrying 0... > 20061013-17:33:04 Device /dev/nst9 - not ready, retrying 1... > ... > 20061013-17:33:34 Device /dev/nst9 - not ready, retrying 30... > 20061013-17:33:35 Device /dev/nst9 - not ready, retrying 31... > 20061013-17:33:36 Parms: /dev/sg14 loaded 2 /dev/nst9 1 > > *** Slot 2 successfully loaded into drive 1. > > 20061013-17:33:36 Doing mtx -f /dev/sg14 1 -- to find what is loaded > 20061013-17:33:47 Parms: /dev/sg14 loaded 0 /dev/nst9 1 > 20061013-17:33:47 Doing mtx -f /dev/sg14 1 -- to find what is loaded > 20061013-17:33:58 Parms: /dev/sg14 loaded 1 /dev/nst8 0 > 20061013-17:33:58 Doing mtx -f /dev/sg14 0 -- to find what is loaded > 20061013-17:34:00 Parms: /dev/sg14 loaded 2 /dev/nst9 1 > 20061013-17:34:00 Doing mtx -f /dev/sg14 1 -- to find what is loaded > 20061013-17:34:05 Parms: /dev/sg14 loaded 2 /dev/nst8 0 > 20061013-17:34:05 Doing mtx -f /dev/sg14 0 -- to find what is loaded > 20061013-17:34:05 Parms: /dev/sg14 unload 1 /dev/nst8 0 > 20061013-17:34:05 Doing mtx -f /dev/sg14 unload 1 0 > > *** Slot 1 successfully unloaded from drive 0. > > 20061013-17:34:58 Parms: /dev/sg14 loaded 1 /dev/nst9 1 > 20061013-17:34:58 Doing mtx -f /dev/sg14 1 -- to find what is loaded > 20061013-17:34:58 Parms: /dev/sg14 load 2 /dev/nst8 0 > 20061013-17:34:58 Doing mtx -f /dev/sg14 load 2 0 > > *** And now there is an attempt to load slot 2 into drive 0, > without an intervening unload of slot 2 from drive 1. > > 20061013-17:34:58 Device /dev/nst8 - not ready, retrying 0... > 20061013-17:34:59 Device /dev/nst8 - not ready, retrying 1... > 20061013-17:35:00 Device /dev/nst8 - not ready, retrying 2... > ... eventually times out ... > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
