Re: [Bacula-devel] Feature request - bscan from bconsole

2009-10-15 Thread Graham Keeling
On Thu, Oct 15, 2009 at 03:56:12PM +0200, Eric Bollengier wrote: > Le Thursday 15 October 2009 15:50:24 Ralf Gross, vous avez écrit : > > Graham Keeling schrieb: > > > On Fri, Oct 09, 2009 at 09:39:55PM +0200, Kern Sibbald wrote: > > > > On Wednesday 07 October 2009 11:02:23 Graham Keeling wrote: >

Re: [Bacula-devel] Feature request - bscan from bconsole

2009-10-15 Thread Graham Keeling
On Thu, Oct 15, 2009 at 03:50:24PM +0200, Ralf Gross wrote: > Graham Keeling schrieb: > > On Fri, Oct 09, 2009 at 09:39:55PM +0200, Kern Sibbald wrote: > > > On Wednesday 07 October 2009 11:02:23 Graham Keeling wrote: > > > > Item n: Run bscan on a remote storage daemon from within bconsole. > > >

Re: [Bacula-devel] Feature request - bscan from bconsole

2009-10-15 Thread Eric Bollengier
Le Thursday 15 October 2009 15:50:24 Ralf Gross, vous avez écrit : > Graham Keeling schrieb: > > On Fri, Oct 09, 2009 at 09:39:55PM +0200, Kern Sibbald wrote: > > > On Wednesday 07 October 2009 11:02:23 Graham Keeling wrote: > > > > Item n: Run bscan on a remote storage daemon from within bconsole

Re: [Bacula-devel] Feature request - bscan from bconsole

2009-10-15 Thread Ralf Gross
Graham Keeling schrieb: > On Fri, Oct 09, 2009 at 09:39:55PM +0200, Kern Sibbald wrote: > > On Wednesday 07 October 2009 11:02:23 Graham Keeling wrote: > > > Item n: Run bscan on a remote storage daemon from within bconsole. > > > Date: 07 October 2009 > > > Origin: Graham Keeling > > > St

Re: [Bacula-devel] Feature request - bscan from bconsole

2009-10-15 Thread Graham Keeling
On Fri, Oct 09, 2009 at 09:39:55PM +0200, Kern Sibbald wrote: > On Wednesday 07 October 2009 11:02:23 Graham Keeling wrote: > > Item n: Run bscan on a remote storage daemon from within bconsole. > > Date: 07 October 2009 > > Origin: Graham Keeling > > Status: Proposing > > > > What: The

Re: [Bacula-devel] Possible bug in SD,

2009-10-15 Thread Arno Lehmann
Hi Kern, 15.10.2009 11:43, Kern Sibbald wrote: > Hello Arno, > > Please open a bug report. There are two things that I would like to see: That's gonna be a problem (as outlined in the original mail): > 1. The exact sequence of commands that lead to the problem I can not reproduce the problem

[Bacula-devel] Bacula scheduler

2009-10-15 Thread Kern Sibbald
Hello, Recently the question came up (during a Bacula course) about whether or not the Bacula scheduler (the part that creates the Job from the Schedule resource) starts jobs according to their Priority if they all have the same start time. The answer is yes, the schedule maintains a list of

Re: [Bacula-devel] Possible bug in SD,

2009-10-15 Thread Kern Sibbald
Hello Arno, Please open a bug report. There are two things that I would like to see: 1. The exact sequence of commands that lead to the problem 2. Debug output set at say 400 on the SD during the period that mtx misbehaves up to the point the SD blows it self up. 3. a traceback (stack dump) p

Re: [Bacula-devel] Possible bug in SD,

2009-10-15 Thread Arno Lehmann
Hi Eric, 15.10.2009 09:40, Eric Bollengier wrote: > Hello Arno, > > Le Thursday 15 October 2009 09:33:21 Arno Lehmann, vous avez écrit : >> Hi, >> >> I just was presented with a SD failure in an assert. >> >> Backups were running, and I changed volumes on an autochanger. After >> the new tapes we

Re: [Bacula-devel] Possible bug in SD,

2009-10-15 Thread Eric Bollengier
Hello Arno, Le Thursday 15 October 2009 09:33:21 Arno Lehmann, vous avez écrit : > Hi, > > I just was presented with a SD failure in an assert. > > Backups were running, and I changed volumes on an autochanger. After > the new tapes were loaded, I did the usualy 'update slots' ceremony: > > *updat

[Bacula-devel] Possible bug in SD,

2009-10-15 Thread Arno Lehmann
Hi, I just was presented with a SD failure in an assert. Backups were running, and I changed volumes on an autochanger. After the new tapes were loaded, I did the usualy 'update slots' ceremony: *update slots scan storage=QuantumDLT drive=0 Connecting to Storage daemon QuantumDLT at gnom:9103 .