Josip:
Your help was stellar. All is working properly. Damned how I missed that
one.
Alan
On 3/8/22 15:12, Josip Deanovic wrote:
On 2022-03-08 19:43, Alan Polinsky wrote:
Josip:
That is obviously the problem, but I'm not sure why it has occurred,
or how to correct it. These are standard LTO2 tapes, that were
previously used in a different setting. I used an mt command, mt -f
/dev/nst0 weof to write an end of file mark at the begining so I could
use bacula to re-label them. All of the tapes are marked with a
maxvolbytes of 53,687,091,200. volbytes is set to 64512 in each of
them. I guess something was changed significantly between the 5.X
version of bacula and 9.6, but it also might be the upgrade of
Slackware. I also don't recall the shoeshine parameter being enabled
in the prior release. In my current setup, which I will probably have
to re-create, my spool files grow quite large.
Thank you for pointing my search to a satisfactory solution.
Ok, now that we know the cause we can devise a solution.
Check your Bacula configuration files for option Maximum Volume Bytes
and remove if from pool resources used for tapes. Don't forget to
reload or restart bacula-dir daemon.
After that, use the update command from bconsole tool. In the
prompt chose the option "Pool from resource".
That option will instruct Bacula to apply current pool configuration
to already created pools.
After that, use the update command again and chose "Volume parameters".
The next step will allow you to chose the option "Maximum Volume Bytes".
After that you will be allowed to chose the pool and the volume name
or ID.
If the number of volumes you need to update is too big for manual
fixing, check the bconsole documentation and help for its update
command. It is possible to select all volumes in a specified pool.
Regards!
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
