Using a positive value for the 'use' size of a holdingdisk definition in
amanda.conf will indeed cause that amount of space to be used if available
and needed for the current run, regardless of what "leftovers" may be on
disk from previous runs. Nothing in the docs suggests otherwise.
The docs don't clarify this one way or the other. I just found it
counter-intuitive and somewhat dangerous as it can cause a full disk in
the case of multiple unflushed backups.
A reasonable workaround for preventing complete filesystem consumption is to
specify a negative value for the 'use' size instead. This will cause Amanda
to believe it can use whatever space is on the disk less that amount, in
effect ensuring that a certain minimum amount of free space is left open.
This is what I've done and it works very well.
Implementing the suggested changes would be a redefinition of upstream
behavior, and after more than 3 years, I'm still not so inclined. Downgrading
this bug to wishlist and tagging it wontfix to reflect that fact.
Okay. What did the amanda teams say about the suggestion?
Brian
( [EMAIL PROTECTED] )
-------------------------------------------------------------------------------
... was no trading on the NYSE today; everybody was happy with what
they had.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
