Package: amanda-common
Version: 1:3.5-1
The lexical taperscan algorithm is supposed to select the next volume to
use based on the lexical ordering of volume labels, but as implemented
in Amanda v3.5 it does not properly restrict the volume labels being
processed to those from the tape pool in question. If multiple tape
pools are in use in a particular configuration, this will cause the
last-used volume in one pool to unexpectedly affect the next volume
selected for use in another pool.
A patch to correct this bug was posted to the amanda-hackers list in
From: Jean-Louis Martineau <jmartin...@carbonite.com>
Subject: Re: lexical.pm last_use_label ignores "storage" field on tapelist
Date: Mon, 12 Mar 2018 14:49:02 +0000
Message-ID:
<cy4pr06mb339853f1748757c2f38a5fcec8...@cy4pr06mb3398.namprd06.prod.outlook.com>
https://marc.info/?l=amanda-hackers&m=152086658119204&w=2
I applied the patch locally and confirmed it solve the problem for me,
but it was never included in an official Amanda release.
Since upstream maintenance of Amanda seems to be paused at the moment,
it might be worth including this fix as a debian/patch in the Debian
Amanda package.
Nathan
