Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Kern Sibbald
On Sunday 15 October 2006 20:08, Michael Brennen wrote: > On Sun, 15 Oct 2006, Kern Sibbald wrote: > > > On Sunday 15 October 2006 17:48, Michael Brennen wrote: > >> > >> I am starting over with a fresh regress checkout and current > >> bacula cvs. I will pay attention to every detail so as to t

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Michael Brennen
On Sun, 15 Oct 2006, Kern Sibbald wrote: > On Sunday 15 October 2006 17:48, Michael Brennen wrote: >> >> I am starting over with a fresh regress checkout and current >> bacula cvs. I will pay attention to every detail so as to try >> and duplicate your test conditions. I may have to change the

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Kern Sibbald
On Sunday 15 October 2006 17:48, Michael Brennen wrote: > On Sun, 15 Oct 2006, Kern Sibbald wrote: > > >> They are essentially the same bug. One was running > >> two-pool-tape, the other 2drive-incremental-2tape, but the mtx > >> logs show the same failure. Consolidating to #687 is fine. > > >

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Michael Brennen
On Sun, 15 Oct 2006, Kern Sibbald wrote: >> They are essentially the same bug. One was running >> two-pool-tape, the other 2drive-incremental-2tape, but the mtx >> logs show the same failure. Consolidating to #687 is fine. > > Well, two-pool-tape runs fine here too, but I didn't realize it >

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Kern Sibbald
On Sunday 15 October 2006 17:22, Michael Brennen wrote: > On Sat, 14 Oct 2006, Kern Sibbald wrote: > > > 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

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Kern Sibbald
On Sunday 15 October 2006 17:14, Michael Brennen wrote: > On Sat, 14 Oct 2006, Kern Sibbald wrote: > > >> 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

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Michael Brennen
On Sat, 14 Oct 2006, Kern Sibbald wrote: > 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

Re: [Bacula-users] An identical two drive failure

2006-10-15 Thread Michael Brennen
On Sat, 14 Oct 2006, Kern Sibbald wrote: >> 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

Re: [Bacula-users] An identical two drive failure

2006-10-14 Thread michael
Kern, if it would help I can set up a VM that you can ssh to work on the real hardware. It may well be too late to try now, as time is so short, perhaps when you return? -- Michael -Original Message- From: Kern Sibbald <[EMAIL PROTECTED]> Subj: Re: [Bacula-users] An ide

Re: [Bacula-users] An identical two drive failure

2006-10-14 Thread Kern Sibbald
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

Re: [Bacula-users] An identical two drive failure

2006-10-14 Thread Kern Sibbald
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. > > I have a totally different autochanger in place now to run the regress tests. > It is a