Udo Kaune schrieb am 07.07.25 um 00:16:
Am 06.07.25 um 07:49 schrieb Dr. Thorsten Brandau via Bacula-users:
Hi
I get the following bacula message (bconsole/message):
06-Jul 07:43 -sd JobId 1512: Error: label.c:993 Expecting Volume
Label, got FI=548700 Stream=SPARSE-DATA len=45816
And my email message is:
05-Jul 23:43 -sd JobId 1512: Please mount append Volume "000020L9" or
label a new one for:
Job: Media.2025-07-05_00.30.00_38
Storage: "LTO9-1" (/dev/nst0)
Pool: Tape
Media type: LTO-9
Again, is your bacula-sd.conf referencing the correct device for tape
drive and autoloader? Did you apply the remediations that were
recommended to you?
Yes, it is referencing (this time...) the right drive. Switched to UUID
so that should be more stable anyway.
After reboot I get the same message:
07-Jul 08:46 -dir JobId 1516: shell command: run BeforeJob
"/usr/libexec/bacula/make_catalog_backup.pl MyCatalog"
07-Jul 08:46 -dir JobId 1516: BeforeJob: mysqldump: Deprecated program
name. It will be removed in a future release, use
'/usr/bin/mariadb-dump' instead
07-Jul 08:46 -dir JobId 1516: Start Backup JobId 1516,
Job=BackupCatalog.2025-07-07_08.45.59_10
07-Jul 08:46 -dir JobId 1516: Using Device "LTO9-1" to write.
07-Jul 08:46 -sd JobId 1516: 3304 Issuing autochanger "load Volume
000020L9, Slot 18, Drive 0" command.
07-Jul 08:48 -sd JobId 1516: 3305 Autochanger "load Volume 000020L9,
Slot 18, Drive 0", status is OK.
07-Jul 08:48 -sd JobId 1516: Error: label.c:993 Expecting Volume Label,
got FI=548700 Stream=SPARSE-DATA len=45816
07-Jul 08:48 -sd JobId 1516: Error: label.c:993 Expecting Volume Label,
got FI=548700 Stream=SPARSE-DATA len=45816
07-Jul 08:49 -sd JobId 1516: Error: label.c:993 Expecting Volume Label,
got FI=548700 Stream=SPARSE-DATA len=45816
07-Jul 08:49 -sd JobId 1516: Error: label.c:993 Expecting Volume Label,
got FI=548700 Stream=SPARSE-DATA len=45816
07-Jul 08:49 -sd JobId 1516: Error: label.c:993 Expecting Volume Label,
got FI=548700 Stream=SPARSE-DATA len=45816
07-Jul 08:49 -sd JobId 1516: Please mount append Volume "000020L9" or
label a new one for:
Job: BackupCatalog.2025-07-07_08.45.59_10
Storage: "LTO9-1" (/dev/nst0)
Pool: Tape
Media type: LTO-9
07-Jul 08:54 -sd JobId 1516: Error: label.c:993 Expecting Volume Label,
got FI=548700 Stream=SPARSE-DATA len=45816
According to the Neo24 tape lib, tape 00020L9 is loaded. There is no
error message in the tape library.
According to the tape it is "full", according to bacula (via webmin ->
volumes in pool) it says "written bytes"=1, "recycle".
From Webmin in the volumes list, I checked that volume and clicked
"delete this volume" assuming that it would delete its contents...
however, it removed it from the list. Yeah, clearer I know, but well,
reading manuals is for the shy.
I am currently trying to get that volume back into the pool, which is
surprisingly difficult.
I issued the "label barcodes" command on the changer and tape pool. This
took some time, then the following messages appeared:
C onnecting to Storage daemon AutoChangerLTO at server06.brace.de:9103 ...
Sending label command for Volume "000003L9" Slot 1 ...
3307 Issuing autochanger "unload Volume 000017L9, Slot 19, Drive 0" command.
3304 Issuing autochanger "load Volume 000003L9, Slot 1, Drive 0" command.
3305 Autochanger "load Volume 000003L9, Slot 1, Drive 0", status is OK.
label.c:993 Expecting Volume Label, got FI=548700 Stream=SPARSE-DATA
len=45816
3920 Cannot label Volume because it is already labeled: "LTOV-0001"
Label command failed for Volume 000003L9.
Media record for Slot 2 Volume "000006L9" already exists.
Media record for Slot 3 Volume "000009L9" already exists.
Media record for Slot 4 Volume "000012L9" already exists.
Media record for Slot 5 Volume "000002L9" already exists.
Media record for Slot 6 Volume "000005L9" already exists.
Media record for Slot 7 Volume "000008L9" already exists.
Media record for Slot 8 Volume "000011L9" already exists.
Media record for Slot 9 Volume "000001L9" already exists.
Media record for Slot 10 Volume "000004L9" already exists.
Media record for Slot 11 Volume "000007L9" already exists.
Media record for Slot 12 Volume "000010L9" already exists.
Media record for Slot 14 Volume "000021L9" already exists.
Media record for Slot 15 Volume "000018L9" already exists.
Media record for Slot 16 Volume "000015L9" already exists.
Media record for Slot 17 Volume "000023L9" already exists.
Sending label command for Volume "000020L9" Slot 18 ...
3307 Issuing autochanger "unload Volume 000003L9, Slot 1, Drive 0" command.
3304 Issuing autochanger "load Volume 000020L9, Slot 18, Drive 0" command.
3305 Autochanger "load Volume 000020L9, Slot 18, Drive 0", status is OK.
label.c:993 Expecting Volume Label, got FI=548700 Stream=SPARSE-DATA
len=45816
3000 OK label. VolBytes=1024 VolABytes=0 VolType=2 Volume="000020L9"
Device="LTO9-1" (/dev/nst0)
Catalog record for Volume "000020L9", Slot 18 successfully created.
Media record for Slot 19 Volume "000017L9" already exists.
Media record for Slot 20 Volume "000014L9" already exists.
Media record for Slot 21 Volume "000022L9" already exists.
Media record for Slot 22 Volume "000019L9" already exists.
Media record for Slot 23 Volume "000016L9" already exists.
Media record for Slot 24 Volume "000013L9" already exists.
Checking back with the pool ("list media") it appears as:
| 26 | 000020L9 | Append | 1 | 1,024 |
0 | 7,776,000 | 1 | 18 | 1 | LTO-9 |
2 | 0 | NULL | NULL |
Still a bit strange, but it was to be recycled anyway, so I assume no
harm done. Hopefully.
BTW: The backup ran, after removing the 20L9 tape, it just switched to
another tape and finished.
So I do hope that this will work out, whenever he wants to use 20L9 next...
Cheers
TB
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
