On Mon, Jan 06, 2020 at 16:13:25 -0500, Chris Hoogendyk wrote:
> I had two jobs running, one started Saturday evening and one started
> Sunday evening. Both holding disks were 100% full. I ran amstatus
> and found that the "current" run was flushing a reasonably large DLE
I was curious if you have a "use" option in place for your holding disk
definitions....
I don't think it would resolve your underlying/original problem (which I
guess is that the taper process dies or soemthing), but it seems like
some of your "cleanup" issues would be avoided if the holiding-disk
filesystems didn't reach 100% usage and thus you avoiding the
empty-"pid"-file situation.
I'm not sure how precisely Amanda is able to control the actual usage as
data streams in from the clients, but if you don't already have a "use"
option in your holding-disk definitions, you might try adding "use -1 gb"
or something like to see if that at least prevents the filesystems
from getting 100% full when this situation hits.... (Presumably you
don't fill up the holding-disk filesystems during a normal run; if you
do come close, you might need "use -200 mb" instead, or whatever.)
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
