Re: [Bacula-users] Device is blocked labeling a Volume

2012-03-01 Thread Tilman Schmidt
Am 01.03.2012 16:58, schrieb Tilman Schmidt: > For lack of a better idea, I have now restarted all Bacula daemons. > That cleared the condition, and I could load and unload tapes again: [...] > The hanging jobs were all gone, of course. They did neither > generate any status mails nor leave any tra

Re: [Bacula-users] Device is blocked labeling a Volume

2012-03-01 Thread Tilman Schmidt
Am 01.03.2012 10:41, schrieb Uwe Schuerkamp: > Hmm, I was "hoping" for some scsi timeouts or similar which might > explain why the device is apparently stuck labelling a tape... do you > have physical access to the device? Any status lights indicating an > error condition (obvious detail, but I'd r

Re: [Bacula-users] Device is blocked labeling a Volume

2012-03-01 Thread Uwe Schuerkamp
On Thu, Mar 01, 2012 at 10:32:18AM +0100, Tilman Schmidt wrote: > Nothing since the last reboot except the normal "Block limits": > > [ts@backup ~]$ dmesg | tail > ADDRCONF(NETDEV_UP): eth0: link is not ready > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > RPC: R

Re: [Bacula-users] Device is blocked labeling a Volume

2012-03-01 Thread Tilman Schmidt
Am 01.03.2012 09:30, schrieb Uwe Schuerkamp: >> Device status: >> Autochanger "HP1x8autoloader" with devices: >>"LTO-3" (/dev/nst0) >> Device "FileStorage" (/tmp) is not open. >> Device "LTO-3" (/dev/nst0) is not open. >> Device is blocked labeling a Volume. >> Drive 0 is not loaded.

Re: [Bacula-users] Device is blocked labeling a Volume

2012-03-01 Thread Uwe Schuerkamp
On Thu, Mar 01, 2012 at 01:28:00AM +0100, Tilman Schmidt wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > CentOS 6 based backup server with Bacula 5.0.0-9.el6 from the CentOS 6 > base repository and an HP 8-slot LTO-3 autochanger, no barcode reader. > This evening's backup jobs are han