I'm confused as to why Volumes are not being created. They do not exist on disk. This is not a newly configured system.
Is "No autolabel because polling" relevant? see below. Said backup has been running for several days. I have confirmed space is available (about 6TB free) and that files can be manually created. Bacula 9.0.6 on FreeBSD with PostgreSQL 9.6.6 After running out of Volumes, I adjusted the configuration files to increase 'Maximum Volumes' from 5060 to 5070.. issued a reload in bconsole, now I see 10 of these: [dan@bacula:~] $ bconsole Connecting to Director bacula.int.unixathome.org:9101 1000 OK: 103 bacula-dir Version: 9.0.6 (20 November 2017) Enter a period to cancel a command. *m 09-Jan 12:44 bacula-dir JobId 269534: Created new Volume="FullAuto-8846", Pool="FullFile", MediaType="FullFile" in catalog. 09-Jan 12:44 bacula-sd-01-sd JobId 269534: Warning: mount.c:215 Open of File device "vDrive-FullFile-8" (/usr/local/bacula/volumes/FullFile) Volume "FullAuto-8846" failed: ERR=file_dev.c:190 Could not open(/usr/local/bacula/volumes/FullFile/FullAuto-8846,OPEN_READ_WRITE,0640): ERR=No such file or directory 09-Jan 12:44 bacula-sd-01-sd JobId 269534: Marking Volume "FullAuto-8846" in Error in Catalog. 09-Jan 12:44 bacula-dir JobId 269534: Created new Volume="FullAuto-8847", Pool="FullFile", MediaType="FullFile" in catalog. 09-Jan 12:44 bacula-sd-01-sd JobId 269534: Warning: mount.c:215 Open of File device "vDrive-FullFile-8" (/usr/local/bacula/volumes/FullFile) Volume "FullAuto-8847" failed: ERR=file_dev.c:190 Could not open(/usr/local/bacula/volumes/FullFile/FullAuto-8847,OPEN_READ_WRITE,0640): ERR=No such file or directory 09-Jan 12:44 bacula-sd-01-sd JobId 269534: Marking Volume "FullAuto-8847" in Error in Catalog. ... After that, the following command was issued, the pool 'max volume' was bumped again, and another reload command issued. *setdebug trace=1 level=200 storage=bacula-sd-01-DailyBackups Connecting to Storage daemon bacula-sd-01-DailyBackups at bacula-sd-01.int.unixathome.org:9103 3000 OK setdebug=200 trace=1 options= tags= *m You have no messages. *m 09-Jan 14:06 bacula-dir JobId 269534: Created new Volume="FullAuto-8856", Pool="FullFile", MediaType="FullFile" in catalog. 09-Jan 14:06 bacula-sd-01-sd JobId 269534: Warning: mount.c:215 Open of File device "vDrive-FullFile-8" (/usr/local/bacula/volumes/FullFile) Volume "FullAuto-8856" failed: ERR=file_dev.c:190 Could not open(/usr/local/bacula/volumes/FullFile/FullAuto-8856,OPEN_READ_WRITE,0640): ERR=No such file or directory 09-Jan 14:06 bacula-sd-01-sd JobId 269534: Marking Volume "FullAuto-8856" in Error in Catalog. * Full output, including the trace, at https://gist.github.com/dlangille/379b9d7784548211bcab936d31e57255 including the 'setdebug trace=1 level=200' output of the SD. Is "No autolabel because polling" relevant. I see that in the output. 'status storage' output includes: Device File: "vDrive-FullFile-8" (/usr/local/bacula/volumes/FullFile) is not open. Device is BLOCKED waiting to create a volume for: Pool: FullFile Media type: FullFile Drive 8 is not loaded. Available Space=7.902 TB == The configuration of that drive is: Device { Name = vDrive-FullFile-8 Media Type = FullFile Archive Device = /usr/local/bacula/volumes/FullFile LabelMedia = yes Random Access = yes AutomaticMount = yes RemovableMedia = no AlwaysOpen = no Autochanger = yes Drive Index = 8 Maximum Concurrent Jobs = 1 Volume Poll Interval = 15 } Ideas? I keep thinking it's something very clearly stated but I am overly looking it. -- Dan Langille - BSDCan / PGCon d...@langille.org ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
