Hi folks,

last night a rather large Backup (about 5TB or so) crashed with the
following error message: 


17-Mär 23:43 localhost-sd JobId 2246: Recycled volume "Offline41" on device 
"LTO4" (/dev/nst0), all previous data lost.
17-Mär 23:43 localhost-sd JobId 2246: New volume "Offline41" mounted on device 
"LTO4" (/dev/nst0) at 17-Mär-2012 23:43.
18-Mär 04:07 archiv-dir JobId 2246: Fatal error: catreq.c:586 attribute create 
error. sql_update.c:501 Update failed: affected_rows=0 for UPDATE Media SET 
InChanger=0, Slot=0 WHERE Slot=41 AND StorageId=2 AND MediaId!=47
23-Mär 03:25 archiv-dir JobId 2246: Error: Watchdog sending kill after 518401 
secs to thread stalled reading File daemon.
23-Mär 03:25 archiv-dir JobId 2246: Fatal error: Network error with FD during 
Backup: ERR=Unterbrechung während des Betriebssystemaufrufs
23-Mär 03:25 archiv-dir JobId 2246: Fatal error: No Job status returned from FD.
23-Mär 03:25 archiv-dir JobId 2246: Error: Bacula archiv-dir 5.2.6 (21Feb12):

Any ideas what could be causing this error? "mtx status" seems to work
fine, so I guess it's not a problem with the autochanger. The backup
runs locally off disks attached to the bacula server itself and is
written to an lto4 library. 


All the best & TIA for your comments, Uwe 

-- 
NIONEX --- Ein Unternehmen der Bertelsmann AG



------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users