On Fri, Jul 02, 2010 at 04:36:52PM -0500, Dustin J. Mitchell wrote:
> On Fri, Jul 2, 2010 at 4:24 PM, Jon LaBadie <[email protected]> wrote:
> > The status seems to say there is no holding disk space available.
> >
> > You've asked to set aside 700GB, does /zvol/amanda/holdingdisk/daily
> > have that much space available?
> >
> > Are the DLEs causing the problem larger than 700GB?
>
> It seems my message did not come through this morning..
>
> Robert is using "define holdingdisk", which just defines the
> holdingdisk. The fix is either
>
> define holdingdisk "foo" { ... }
> holdingdisk "foo"
>
> or just
>
> holdingdisk "foo" { ... }
>
I suspect the documentation is lagging behind development.
Looking at the manpages I was unable to answer these questions.
If the 'define holdingdisk "name"' syntax is used, are you saying
the 'holdingdisk "name"' directive must be used to specify which
defined hd to use?
If multiple 'define holdingdisk "name"' are specified, can a
dumptype use any collection of them with multiple 'holdingdisk "name"'
directives? Or, can multiple "name(s)" go on the same line?
Is there a reason that holdingdisk {yes|required} does not imply
use any and all defined holdingdisks?
--
Jon H. LaBadie [email protected]
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
