I have no ideas, but I can confirm that I'm seeing the same behavior. I
can minimize it by increasing the timeout value to 7200, but I still see
about two dump failures a week from timeout (always the largest
dumps--but not even close to tape capacity). I can elimate as describe
by the original poster (but it only works the first time :( ) on the one
dump that fails.
I'm using FreeBSD 4.5-STABLE on an AMD Duron 1300 with an AIWA NS-20
tape drive and Amanda 2.4.3b2.
On Wed, 2002-03-20 at 14:06, david wang wrote:
> Hi,
>
> I had the Amanda backup server 2.4.2p2 running well for few months on
> Linux systems except some FreeBSD clients gave me problem from time to
> time. One of the FreeBSD client can only be backed up when I start with
> new configuration. The next time you run amdump with this configuration,
> Amanda will fail with timeout errors. If I delete all the log files for
> this config, Amanda can backup successfully too. The FreeBSD 3.1 client
> is using DUMP to archive file systems.
>
> Does anyone have any clue for this problems?
>
> Thanks a lot.
>
> David Wang
> Systems Admin @ IMC
>
--
_
| |V| / ' || MacroHard -- \
\_| | | \_, || the perfection of form over |
----------------------------------|| substance, marketing over |
Web: http://www.borgsdemons.com || performance, and greed over |
AIM: johnmcooper || design . . . |
=====================================================================/
Public Key: http://www.borgsdemons.com/Personal/pgpkey.asc |
=====================================================================\