Storage blocked waiting to create a volume that has been created

[Natalio Gatti]

I have a working bareos with 3 file storages and 15 clients. Each client is configured to save data on one particular storage.
My Volumes are labeled automatically, each with only one backup:

Label Format = "${JobId}-${Job}-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}-${Level}"

Some times, one storage becomes blocked, waiting for a volume that was already created, and I have to manually create an other volume so as to continue. I am trying to solve this problem, so no manual intervention will be required.

I can see this logs:
#####################
29-Aug 00:17 SERVER1-dir JobId 2090: Start Backup JobId 2090, Job=Backup-SERVER2_mysql.2016-08-29_00.01.00_08
29-Aug 00:17 SERVER1-dir JobId 2090: Created new Volume "2090-Backup-SERVER2_mysql-2016-08-29-Differential" in catalog.
29-Aug 00:17 SERVER1-dir JobId 2090: Using Device "FileStorage" to write.
29-Aug 00:17 SERVER2-fd JobId 2090: shell command: run ClientBeforeJob "/etc/bareos/scripts/mysqldump_crea.sh"
29-Aug 00:17 SERVER2-fd JobId 2090: ClientBeforeJob: mysql: [Warning] Using a password on the command line interface can be insecure.
29-Aug 00:17 SERVER2-fd JobId 2090: ClientBeforeJob: mysqldump: [Warning] Using a password on the command line interface can be insecure.
29-Aug 00:20 SERVER2-fd JobId 2090: ClientBeforeJob: mysqldump: [Warning] Using a password on the command line interface can be insecure.
29-Aug 00:20 SERVER1-dir JobId 2090: Error: sql_create.c:450 Volume "2090-Backup-SERVER2_mysql-2016-08-29-Differential" already exists.
29-Aug 00:20 SERVER1-dir JobId 2090: Error: sql_create.c:450 Volume "2090-Backup-SERVER2_mysql-2016-08-29-Differential" already exists.
29-Aug 00:20 SERVER1-sd JobId 2090: Job Backup-SERVER2_mysql.2016-08-29_00.01.00_08 is waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
Storage: "FileStorage" (/data/bareos)
Pool: Pool-Diff
Media type: File
29-Aug 00:30 SERVER1-dir JobId 2090: Error: sql_create.c:450 Volume "2090-Backup-SERVER2_mysql-2016-08-29-Differential" already exists.
#####################

And via bconsole I get this status storage:
#####################
Device status:
Device "FileStorage" (/data/bareos) is not open.
Device is BLOCKED waiting to create a volume for:
Pool: Pool-Diff
Media type: File
#####################

The file was not created, but the volume exists in the database. I really have no clue...

Thanks.

[Natalio Gatti]

Today again, an other job was blocked. These are the logs:
######################
30-Aug 00:15 SERVER1-dir JobId 2140: Start Backup JobId 2140, Job=Backup-SERVER2_mysql.2016-08-30_00.01.01_02
30-Aug 00:15 SERVER1-dir JobId 2140: Created new Volume "2140-Backup-SERVER2_mysql-2016-08-30-Differential" in catalog.
30-Aug 00:15 SERVER1-dir JobId 2140: Using Device "FileStorage" to write.
30-Aug 00:15 SERVER2-fd JobId 2140: shell command: run ClientBeforeJob "/etc/bareos/scripts/mysqldump_crea.sh"
30-Aug 00:15 SERVER2-fd JobId 2140: ClientBeforeJob: -- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
30-Aug 00:17 SERVER1-dir JobId 2140: Error: sql_create.c:450 Volume "2140-Backup-SERVER2_mysql-2016-08-30-Differential" already exists.
30-Aug 00:17 SERVER1-dir JobId 2140: Error: sql_create.c:450 Volume "2140-Backup-SERVER2_mysql-2016-08-30-Differential" already exists.
30-Aug 00:17 SERVER3-sd JobId 2140: Job Backup-SERVER2_mysql.2016-08-30_00.01.01_02 is waiting. Cannot find any appendable volumes.

Please use the "label" command to create a new Volume for:

Storage: "FileStorage" (/backup/)

Pool: Pool-Diff
Media type: File

######################

I can see the volume created in the database:
######################
select MediaId,VolumeName,MediaType,FirstWritten,LastWritten from Media where VolumeName="2140-Backup-ministeriodb.asso.com.ar_mysql-2016-08-30-Differential";
+---------+--------------------------------------------------------------------+-----------+---------------------+---------------------+
| MediaId | VolumeName | MediaType | FirstWritten | LastWritten |
+---------+--------------------------------------------------------------------+-----------+---------------------+---------------------+
| 1933 | 2140-Backup-ministeriodb.asso.com.ar_mysql-2016-08-30-Differential | File | 2016-08-30 00:17:07 | 2016-08-30 00:28:40 |
+---------+--------------------------------------------------------------------+-----------+---------------------+---------------------+
######################

But no file was created on the storage:
######################
root@backup /backup # ls -la 2140*
ls: cannot access 2140*: No such file or directory
######################

Could this strange behaviour be a misconfiguration on my side? Which parameters should I look for?

Thanks.

[Natalio Gatti]

Again, today an other job was blocked with the same reason.

Is this a common error or a misconfiguration on my side? This is happening with jobs that run scripts (mysqldumps). Maybe a bug in the label system?
I really appreciate any help.

Thanks.

[kf0...@gmail.com]

Is "/data/bareos" a network mount?