I have a "Migrate to Tape" job that gets run manually, and copies
backups that have been made into a disk-backed store, mounted as
/srv/filepools, onto tapes in the IBM TS4300 autochanger.
Someone else has been "doing things with it" since I first set
things up, but haven't invoked the manual job, so I've just run
it, and I've seen it reporting the following:
15-Oct 14:02 mysrvr-sd JobId 1309: Volume "000003L9" previously written, moving
to end of data.
15-Oct 14:03 mysrvr-sd JobId 1309: Error: Unable to position to end of data on
Tape device "TS4300-Drive1" (/dev/IBMtape1n): ERR=tape_dev.c:366 ioctl MTIOCGET
error on "TS4300-Drive1" (/dev/IBMtape1n). ERR=Success.
15-Oct 14:03 mysrvr-sd JobId 1309: Marking Volume "000003L9" in Error in
Catalog.
15-Oct 14:03 mysrvr-sd JobId 1309: 3307 Issuing autochanger "unload Volume
000003L9, Slot 3, Drive 0" command.
15-Oct 14:05 mysrvr-sd JobId 1309: 3304 Issuing autochanger "load Volume
000004L9, Slot 4, Drive 0" command.
15-Oct 14:06 mysrvr-sd JobId 1309: 3305 Autochanger "load Volume 000004L9, Slot
4, Drive 0", status is OK.
15-Oct 14:06 mysrvr-sd JobId 1309: Wrote label to prelabeled Volume "000004L9"
on Tape device "TS4300-Drive1" (/dev/IBMtape1n)
15-Oct 14:06 mysrvr-sd JobId 1308: Ready to read from volume "VolCP-0009" on
File device "FileChgr2-Dev1" (/srv/filepools).
15-Oct 14:06 mysrvr-sd JobId 1310: Ready to read from volume "VolCP-0009" on
File device "FileChgr2-Dev2" (/srv/filepools).
15-Oct 14:06 mysrvr-sd JobId 1308: Forward spacing Volume "VolCP-0009" to
addr=918419075
15-Oct 14:06 mysrvr-sd JobId 1310: Forward spacing Volume "VolCP-0009" to
addr=970402780
I'm not quite able to equate the
"ERR=Success"
with the
"Error: Unable to position to end of data on Tape device"
however, the third Tape (Volume) does now show as being in an Error state,
so maybe the "ERR=Success" relates to the Error being reported successfully?
This has happened before, leaving Volumes showing as in Error, albeit then
going on to put data on the next Tape/Volume in the Pool.
FWIW, a cutdown 'list volumes' output shows
+----+------------+--------+-------------+-----+------------+-----+---------------------+------------+
| id | volumename | status | volbytes | fil | retention | slt | lastwritten
| expiresin |
+----+------------+--------+-------------+-----+------------+-----+---------------------+------------+
| 10 | 000000L9 | Error | 153,216,000 | 2 | 31,536,000 | 1 | 2025-12-10
10:10:24 | 4,820,045 |
| 11 | 000001L9 | Error | 258,048 | 1 | 31,536,000 | 2 | 2026-06-15
13:53:49 | 20,990,250 |
| 12 | 000003L9 | Error | 999,936,000 | 1 | 31,536,000 | 3 | 2026-08-27
19:28:31 | 27,317,532 |
| 13 | 000004L9 | Append | 5,935,104 | 0 | 31,536,000 | 4 | 2026-10-15
14:16:21 | 31,532,402 |
| 14 | 000005L9 | Append | 64,512 | 0 | 31,536,000 | 5 |
| 0 |
+----+------------+--------+-------------+----+------------+------+---------------------+------------+
and where the writing to 000004L9 is still ongong as I type.
Any pointers/experiences with similar outputs and/or Errors/ERR?
For bonus points, I should say that I also find the
"Wrote label to prelabeled Volume"
a bit confusing too?
Kevin Buckley
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
