Hi,

29.10.2007 11:41,, Gary Stainburn wrote::
> On Saturday 27 October 2007 14:46, Arno Lehmann wrote:
>> At this point, what is the 'sta sd=larry2-leeds' output?
>> Normally, things should work now, I think...
>>
>> Arno
> 
> As you can see below, it still says it's blocked.  It also says there's 4 
> jobs 
> writing to it too which I don't understand. I thought you could onnly have 
> one job per device.
No, more than one job can use a device simultaneously. Of course, 
internally, Bacula has to sequence the actual write operations, but 
non the less, jobs as a whole can run simultaneously.

You set this up in the configuration, by the way - by default, job 
concurrency is not enabled.

> Any ideas anyone?
> 
> Gary
> 
> *sta sd=larry2-leeds
> Connecting to Storage daemon larry2-leeds at larry2.ringways.co.uk:9103
> 
> larry2-sd Version: 2.2.4 (14 September 2007) i686-pc-linux-gnu redhat
> Daemon started 19-Oct-07 16:56, 143 Jobs run since started.
>  Heap: heap=872,448 smbytes=641,805 max_bytes=707,072 bufs=215 max_bufs=222
> Sizes: boffset_t=8 size_t=4 int32_t=4 int64_t=8
> 
> Running Jobs:
> Writing: Differential Backup job ladmin9 JobId=491 Volume=""
>     pool="Leeds" device="LeedsStorage" (/var/bacula/leeds)
>     spooling=0 despooling=0 despool_wait=0
>     Files=0 Bytes=0 Bytes/sec=0
>     FDReadSeqNo=6 in_msg=6 out_msg=4 fd=6
> Writing: Full Backup job ladmin1 JobId=649 Volume="leeds0040"
>     pool="Leeds" device="LeedsStorage" (/var/bacula/leeds)
>     spooling=0 despooling=0 despool_wait=0
>     Files=0 Bytes=0 Bytes/sec=0
>     FDReadSeqNo=6 in_msg=6 out_msg=5 fd=8
> Writing: Full Backup job ladmin2 JobId=650 Volume="leeds0044"
>     pool="Leeds" device="LeedsStorage" (/var/bacula/leeds)
>     spooling=0 despooling=0 despool_wait=0
>     Files=0 Bytes=0 Bytes/sec=0
>     FDReadSeqNo=6 in_msg=6 out_msg=5 fd=10
> Writing: Incremental Backup job ladmin7 JobId=653 Volume="leeds0044"
>     pool="Leeds" device="LeedsStorage" (/var/bacula/leeds)
>     spooling=0 despooling=0 despool_wait=0
>     Files=0 Bytes=0 Bytes/sec=0
>     FDReadSeqNo=6 in_msg=6 out_msg=4 fd=12
> ====

As we see (Files= Bytes=) all these jobs actually don't transfer data 
but rather wait for something to happen.

In this case, I think the SD is currently trying to create a volume. I 
assume this because there are different volume names active, which can 
only happen while one job noticed that it needed another volume, and 
the others simply have to wait, but are not yet informed of the volume 
change.

> Jobs waiting to reserve a drive:
> ====
> 
> Terminated Jobs:
>  JobId  Level    Files      Bytes   Status   Finished        Name
> ===================================================================
>    643  Full          0         0   Other    26-Oct-07 14:10 lpartsl
>    644  Incr         91    168.8 M  OK       26-Oct-07 14:12 lserv1
>    645  Incr         99    71.41 M  OK       26-Oct-07 14:13 lserv4
>    646  Incr        133    978.9 M  OK       26-Oct-07 14:16 lserv6
>    647  Incr         88    560.7 M  OK       26-Oct-07 14:18 lserv9
>    648  Incr        186    127.5 M  OK       26-Oct-07 14:19 lservg
>    676  Incr        122    1.200 G  OK       26-Oct-07 15:43 dadmin1
>    677  Incr         78    283.4 M  OK       26-Oct-07 16:04 dadmin4
>    651  Full          0         0   Other    26-Oct-07 16:58 ladmin4
>    652  Incr          0         0   Other    26-Oct-07 17:28 ladmin6
> ====
> 
> Device status:
> Device "LeedsStorage" (/var/bacula/leeds) is not open.
>     Device is BLOCKED waiting to create a volume for:
>        Pool:        Leeds
>        Media type:  leeds-tape
> Device "HalesStorage" (/var/bacula/hales) is not open.
> Device "PrimaStorage" (/var/bacula/prima) is not open.
> Device "DoncStorage" (/var/bacula/donc) is not open.
> ====

Currently, Bacula tries to create a volume automatically, or waits for 
user intervention.

> In Use Volume status:
> leeds0044 on device "LeedsStorage" (/var/bacula/leeds)
>     Reader=0 writers=0 reserved=4
> ====

Here you can see that the four jobs reported above wait for a volume 
to become available.

> ====
> *            

What happens if you try to create a volume manually? This output looks 
like automatic volume creation failed, but there should be a more 
detailed operator request mail.

Of course, the console messages or the console log file should have 
more information, too.

If they don't, I recommend to set debug output tracing with a command 
like 'setdebug level=200 trace=1 sd=larry2-leeds', issue a mount 
command, and then inspect the trace file, if you don't get anything 
useful in the messages.

Arno

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to