On Wed, 12 Feb 2003 at 10:10am, Bill Hults wrote

> planner: time 0.113: setting up estimates for BS1://ADS1/AMRightFax
> BS1://ADS1/AMRightFax overdue 12095 days for level 0
> setup_estimate: BS1://ADS1/AMRightFax: command 0, options:
>     last_level -1 next_level0 -12095 level_days 0
>     getting estimates 0 (0) -1 (-1) -1 (-1)

That's obviously a bad estimate.

> INFO planner Adding new disk hsp-db:/db/backup/hsp.
> INFO planner Adding new disk BS1://ADS1/AMRightFax.
> ERROR planner BS1NAK :  amandad busy

That's bad as well.

> There is a line in /tmp/amanda/amtrmidx about not being able to open the
> directory the index was in. The directory wasn't created presumable since it
> didn't do a backup of the share.
> That seems to be the only pertinent message in /tmp/amanda.
> Anyone have any ideas as to what might be causing this behavior?

What does amcheck have to say about your config?  On BS1 (which I'm 
assuming is the Linux samba host), do you see stale, leftover amanda 
processes?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University