24.0.1~pre27: Max Volume jobs=1 exceeded. Marking Volume "000017L9" as Used.

34 views
Skip to first unread message

Ami Sil

unread,
Jan 26, 2025, 5:57:15 AMJan 26
to bareos-users
I have set in the Pool:

Maximum Volume Jobs = 0
or 
Maximum Volume Jobs = 100

But when a backup starts on the tape device, I get the messages:

Max Volume jobs=1 exceeded. Marking Volume "000017L9" as Used.
Max Volume jobs=1 exceeded. Marking Volume "000016L9" as Used.
Max Volume jobs=1 exceeded. Marking Volume "000019L9" as Used.

How can this be solved?

Thanks, Amihai 

Ami Sil

unread,
Jan 26, 2025, 6:35:24 AMJan 26
to bareos-users
Here is the full log of this problem.
Please see also my pool setting
Pool {
  Name = LTO-Pool00
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes

  Maximum Volume Jobs = 100
  Volume Retention = 3650 days
  #Maximum Volume Bytes = 18T
  #Label Format = "LTO-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}-${NumVols}"
}

18

2025-01-26 13:15:53

bareos-sd JobId 1067: Job rabino_pmvlab_edri_asus.2025-01-26_13.15.24_02 is waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "tapedrive-0" (/dev/IBMtape0n)
Pool: LTO-Pool01
Media type: LTO

17

2025-01-26 13:15:53

bareos-sd JobId 1067: Version: 24.0.1~pre27.250812184 (24 January 2025) Red Hat Enterprise Linux release 9.5 (Plow)

16

2025-01-26 13:15:53

rabino-fd JobId 1067: ACL support is enabled

15

2025-01-26 13:15:53

rabino-fd JobId 1067: Extended attribute support is enabled

14

2025-01-26 13:15:52

rabino-fd JobId 1067: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

13

2025-01-26 13:15:52

rabino-fd JobId 1067: Connected Storage daemon at 132.68.130.81:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

12

2025-01-26 13:15:26

bareos-dir JobId 1067: Using Device "tapedrive-0" to write.

11

2025-01-26 13:15:26

bareos-dir JobId 1067: Max Volume jobs=1 exceeded. Marking Volume "000019L9" as Used.

10

2025-01-26 13:15:26

bareos-dir JobId 1067: Max Volume jobs=1 exceeded. Marking Volume "000016L9" as Used.

9

2025-01-26 13:15:26

bareos-dir JobId 1067: Max Volume jobs=1 exceeded. Marking Volume "000017L9" as Used.

8

2025-01-26 13:15:26

bareos-dir JobId 1067: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

7

2025-01-26 13:15:26

bareos-dir JobId 1067: Handshake: Immediate TLS

6

2025-01-26 13:15:26

bareos-dir JobId 1067: Connected Client: rabino-fd at 132.68.130.81:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

5

2025-01-26 13:15:26

bareos-dir JobId 1067: Probing client protocol... (result will be saved until config reload)

4

2025-01-26 13:15:26

bareos-dir JobId 1067: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

3

2025-01-26 13:15:26

bareos-dir JobId 1067: Connected Storage daemon at 132.68.130.81:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

2

2025-01-26 13:15:26

bareos-dir JobId 1067: Start Backup JobId 1067, Job=rabino_pmvlab_edri_asus.2025-01-26_13.15.24_02

1

2025-01-26 13:15:26

bareos-dir JobId 1067: Version: 24.0.1~pre27.250812184 (24 January 2025) Ubuntu 22.04.5 LTS

Ami Sil

unread,
Jan 26, 2025, 9:40:33 AMJan 26
to bareos-users
I have found that the "Maximum Volume Jobs" of each tape volume can be changed in bconsole update. I have changed the "Maximum Volume Jobs" parameters to "0" for my tapes and start a backup. But now, all the tapes failed with the error:

 Error: Unable to position to end of data on device "tapedrive-1"...
Marking Volume "000017L9" in Error in Catalog

These tapes were OK, backup jobs were written to these tapes, and the backups ended with no errors. 
What is the problem now?

Here is the full log of the last backup before I cancelled it:



30

2025-01-26 16:30:13

bareos-sd JobId 1071: 3307 Issuing autochanger "unload slot 9, drive 1" command.

29

2025-01-26 16:30:13

bareos-sd JobId 1071: Marking Volume "000019L9" in Error in Catalog.

28

2025-01-26 16:30:13

bareos-sd JobId 1071: Error: Unable to position to end of data on device "tapedrive-1" (/dev/IBMtape1n): ERR=backends/generic_tape_device.cc:207 ioctl MTIOCGET error on "tapedrive-1" (/dev/IBMtape1n). ERR=Success.


27

2025-01-26 16:28:10

bareos-sd JobId 1071: Moving to end of data on volume "000019L9"

26

2025-01-26 16:28:07

bareos-sd JobId 1071: 3305 Autochanger "load slot 9, drive 1", status is OK.

25

2025-01-26 16:27:34

bareos-sd JobId 1071: 3304 Issuing autochanger "load slot 9, drive 1" command.

24

2025-01-26 16:26:09

bareos-sd JobId 1071: 3307 Issuing autochanger "unload slot 6, drive 1" command.

23

2025-01-26 16:26:09

bareos-sd JobId 1071: Marking Volume "000016L9" in Error in Catalog.

22

2025-01-26 16:26:09

bareos-sd JobId 1071: Error: Unable to position to end of data on device "tapedrive-1" (/dev/IBMtape1n): ERR=backends/generic_tape_device.cc:207 ioctl MTIOCGET error on "tapedrive-1" (/dev/IBMtape1n). ERR=Success.


21

2025-01-26 16:25:24

bareos-sd JobId 1071: Moving to end of data on volume "000016L9"

20

2025-01-26 16:25:21

bareos-sd JobId 1071: 3305 Autochanger "load slot 6, drive 1", status is OK.

19

2025-01-26 16:24:46

bareos-sd JobId 1071: 3304 Issuing autochanger "load slot 6, drive 1" command.

18

2025-01-26 16:20:52

bareos-sd JobId 1071: 3307 Issuing autochanger "unload slot 7, drive 1" command.

17

2025-01-26 16:20:52

bareos-sd JobId 1071: Marking Volume "000017L9" in Error in Catalog.

16

2025-01-26 16:20:52

bareos-sd JobId 1071: Error: Unable to position to end of data on device "tapedrive-1" (/dev/IBMtape1n): ERR=backends/generic_tape_device.cc:207 ioctl MTIOCGET error on "tapedrive-1" (/dev/IBMtape1n). ERR=Success.


15

2025-01-26 16:19:48

bareos-sd JobId 1071: Moving to end of data on volume "000017L9"

14

2025-01-26 16:19:28

bareos-sd JobId 1071: Version: 24.0.1~pre27.250812184 (24 January 2025) Red Hat Enterprise Linux release 9.5 (Plow)

13

2025-01-26 16:19:28

rabino-fd JobId 1071: ACL support is enabled

12

2025-01-26 16:19:28

rabino-fd JobId 1071: Extended attribute support is enabled

11

2025-01-26 16:19:28

rabino-fd JobId 1071: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

10

2025-01-26 16:19:28

rabino-fd JobId 1071: Connected Storage daemon at 132.68.130.81:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

9

2025-01-26 16:19:02

bareos-dir JobId 1071: Using Device "tapedrive-1" to write.

8

2025-01-26 16:19:02

bareos-dir JobId 1071: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

7

2025-01-26 16:19:02

bareos-dir JobId 1071: Handshake: Immediate TLS

6

2025-01-26 16:19:02

bareos-dir JobId 1071: Connected Client: rabino-fd at 132.68.130.81:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

5

2025-01-26 16:19:02

bareos-dir JobId 1071: Probing client protocol... (result will be saved until config reload)

4

2025-01-26 16:19:02

bareos-dir JobId 1071: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

3

2025-01-26 16:19:02

bareos-dir JobId 1071: Connected Storage daemon at 132.68.130.81:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

2

2025-01-26 16:19:02

bareos-dir JobId 1071: Start Backup JobId 1071, Job=rabino_pmvlab_edri_asus.2025-01-26_16.18.59_03

1

2025-01-26 16:19:01

bareos-dir JobId 1071: Version: 24.0.1~pre27.250812184 (24 January 2025) Ubuntu 22.04.5 LTS




Ami Sil

unread,
Jan 27, 2025, 2:15:33 AMJan 27
to bareos-users
I try to write an eof mark on one of the problematic tapes. 
I try with one tape:
mt -f /dev/IBMtape0n eod
mt -f /dev/IBMtape0n weof

now I try to check with btape but gets an error:

btape  /dev/IBMtape0n
*status
 Bareos status: file=0 block=0
 Device status: BOT ONLINE file=-1 block=0
Device status: TAPE BOT ONLINE. ERR=
*eod
btape: stored/btape.cc:627-0 backends/generic_tape_device.cc:207 ioctl MTIOCGET error on "tapedrive-0" (/dev/IBMtape0n). ERR=Success.

Is there any bug in the generic_tape_device.cc code ? 
Thanks, Amihai

Sebastian Sura

unread,
Jan 27, 2025, 4:02:05 AMJan 27
to bareos...@googlegroups.com

Hi Amihai

this looks like a very weird error.  Could you execute the btape command again but with debug level 1000 ? I.e.

btape -d1000 --verbose /dev/IBMtape0n

The output of this would be very helpful when trying to track down your issue.

Kind Regards
Sebastian Sura

Am 27.01.25 um 08:15 schrieb Ami Sil:
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bareos-users/f0d02040-967c-4e6f-b67e-6e0f6fd6d2c4n%40googlegroups.com.
-- 
 Sebastian Sura                  sebasti...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-0
 https://www.bareos.com
 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz

Bruno Friedmann (bruno-at-bareos)

unread,
Jan 30, 2025, 9:36:13 AMJan 30
to bareos-users
Sebastian this is due to the lintape driver.

Ami as sent in email, please contact sales at bareos if you want to get a quote for adding lintape driver to bareos. Bareos is known to work well with the traditional st kernel driver and LTO9 tapes.
Reply all
Reply to author
Forward
0 new messages