On Tue, Feb 2, 2010 at 11:16 AM, Bob Hetzel <b...@case.edu> wrote: > > > John Drescher wrote: >> >> On Tue, Feb 2, 2010 at 10:58 AM, Bob Hetzel <b...@case.edu> wrote: >>> >>> Greetings, >>> >>> I've just upgraded to 5.0.0 and have run into this odd issue. Bacula >>> seems >>> to be stuck waiting for a labeled volume, even after it attempts to label >>> a >>> new volume. The bconsole messages seem to reflect this loop... >>> >>> *mess >>> 02-Feb 10:32 claustrum-sd JobId 3583: Error: block.c:1012 Read error on >>> fd=9 at file:blk 0:0 on device "IBMLTO4-0" (/dev/nst0). ERR=Device or >>> resource busy. >>> 02-Feb 10:32 claustrum-sd JobId 3583: Labeled new Volume "LTO429L4" on >>> device "IBMLTO4-0" (/dev/nst0). >>> 02-Feb 10:33 claustrum-sd JobId 3583: Error: block.c:1012 Read error on >>> fd=9 at file:blk 0:0 on device "IBMLTO4-0" (/dev/nst0). ERR=Device or >>> resource busy. >>> 02-Feb 10:33 claustrum-sd JobId 3583: Labeled new Volume "LTO429L4" on >>> device "IBMLTO4-0" (/dev/nst0). >>> 02-Feb 10:33 claustrum-sd JobId 3583: Error: block.c:1012 Read error on >>> fd=9 at file:blk 0:0 on device "IBMLTO4-0" (/dev/nst0). ERR=Device or >>> resource busy. >>> 02-Feb 10:33 claustrum-sd JobId 3583: Labeled new Volume "LTO429L4" on >>> device "IBMLTO4-0" (/dev/nst0). >>> >>> The tape in question, LTO429L4 is new and never used before. Here's the >>> list volumes output for it >>> >>> | 48 | LTO429L4 | Append | 1 | 0 | >>> 0 >>> | 10,368,000 | 1 | 39 | 1 | LTO | 0000-00-00 >>> 00:00:00 | >>> +- >>> >>> *status storage >>> Automatically selected Storage: Dell-ML6000 >>> Connecting to Storage daemon Dell-ML6000 at claustrum:9103 >>> >>> claustrum-sd Version: 5.0.0 (26 January 2010) x86_64-unknown-linux-gnu >>> ubuntu 9.10 >>> Daemon started 02-Feb-10 09:36, 0 Jobs run since started. >>> Heap: heap=2,592,768 smbytes=2,274,219 max_bytes=2,306,226 bufs=168 >>> max_bufs=174 >>> Sizes: boffset_t=8 size_t=8 int32_t=4 int64_t=8 >>> >>> Running Jobs: >>> Writing: Incremental Backup job pituitary JobId=3583 Volume="LTO429L4" >>> pool="Westwing" device="IBMLTO4-0" (/dev/nst0) >>> spooling=0 despooling=0 despool_wait=0 >>> Files=0 Bytes=0 Bytes/sec=0 >>> FDReadSeqNo=6 in_msg=6 out_msg=4 fd=5 >>> Writing: Incremental Backup job cortex JobId=3584 Volume="LTO428L4" >>> pool="Westwing" device="IBMLTO4-1" (/dev/nst1) >>> spooling=0 despooling=0 despool_wait=0 >>> Files=0 Bytes=0 Bytes/sec=0 >>> FDReadSeqNo=6 in_msg=6 out_msg=4 fd=7 >>> ==== >>> >>> Jobs waiting to reserve a drive: >>> ==== >>> >>> Terminated Jobs: >>> <content deleted> >>> ==== >>> >>> Device status: >>> Autochanger "Dell-ML6000" with devices: >>> "IBMLTO4-0" (/dev/nst0) >>> "IBMLTO4-1" (/dev/nst1) >>> Device "IBMLTO4-0" (/dev/nst0) open but no Bacula volume is currently >>> mounted. >>> Device is being initialized. >>> Slot 39 is loaded in drive 0. >>> Total Bytes Read=0 Blocks Read=0 Bytes/block=0 >>> Positioned at File=0 Block=0 >>> Device "IBMLTO4-1" (/dev/nst1) open but no Bacula volume is currently >>> mounted. >>> Device is being initialized. >>> Slot 38 is loaded in drive 1. >>> Total Bytes Read=0 Blocks Read=0 Bytes/block=0 >>> Positioned at File=0 Block=0 >>> ==== >>> >>> Used Volume status: >>> >> >> To me this is not a problem with labeling but a problem with the >> mtx-changer script not waiting for your changer to finish. Did your >> autochanger pass the changer tests? >> >> John > > This is not a new implementation, it's an upgrade. >
Did you have to modify the old mtx-changer? -- John M. Drescher ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users