I am running bacula 2.4.3 with an IBM TS3100 autochanger. The setup has
been running fine for a year, but we've recently added a third tape to
each pool, and since then bacula happy writes to the first two tapes,
but then refuses to go any further, even though the third tape has
status 'purged':
*list volumes pool=D07
+---------+------------+-----------+---------+-------------------+----------+--------------+---------+------+-----------+-----------+---------------------+
| MediaId | VolumeName | VolStatus | Enabled | VolBytes |
VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType |
LastWritten |
+---------+------------+-----------+---------+-------------------+----------+--------------+---------+------+-----------+-----------+---------------------+
| 13 | D07T01L4 | Full | 1 | 977,821,601,792 |
979 | 31,536,000 | 1 | 9 | 1 | LTO-4 | 2008-10-27
17:54:01 |
| 14 | D07T02L4 | Full | 1 | 1,028,699,318,272 |
1,029 | 31,536,000 | 1 | 5 | 1 | LTO-4 |
2008-10-27 22:16:24 |
| 78 | D07T03L4 | Purged | 1 | 201,611,816,960 |
203 | 31,536,000 | 0 | 1 | 1 | LTO-4 | 2008-10-01
22:56:43 |
+---------+------------+-----------+---------+-------------------+----------+--------------+---------+------+-----------+-----------+---------------------+
The device is "blocked", from "status storage":
Device status:
Autochanger "Autochanger" with devices:
"Drive1" (/dev/nst0)
Device "Drive1" (/dev/nst0) is not open.
Device is BLOCKED waiting to create a volume for:
Pool: D07
Media type: LTO-4
Drive 0 is not loaded.
====
Issuing a 'mount' command returns without it even trying to do anything
with mtx-changer.
*mount
Automatically selected Storage: Autochanger
Enter autochanger slot: 1
3001 OK mount. Device="Drive1" (/dev/nst0)
Then it just complains that it can't find any appendable volumes:
*mes
28-Oct 10:40 tabasco-sd JobId 1005: Job test0.2008-10-27_12.25.16
waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "Drive1" (/dev/nst0)
Pool: D07
Media type: LTO-4
I can issue mount commands forever and it won't do anything different. I
have tried debugging this by enabling the debugging in the storage
daemon to '200', but didn't get any further. Maybe I need to increase it
in the director too?
Some combination of manually 'delete', 'mt -f /dev/nst0 weof' and
'label' will eventually get it working again, but this usually takes
about 20 minutes of messing around. This is happening for every single
job. I had this problem in 2.2.8 too; I upgraded to 2.4.3 in the hope of
fixing this problem, but unfortunately the problem remains.
Grateful for any help...
--
Chris Howells <chris AT transitive DOT com>
Senior SysAdmin - Transitive Ltd.
http://www.transitive.com
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
