On Sunday 11 July 2004 15:49, fmouse AT fmp DOT com wrote:
>Thus spake Gene Heskett on Sun, Jul 11, 2004 at 04:29:31AM CDT
>
>> On Sunday 11 July 2004 03:11, fmouse-amanda AT fmp DOT com wrote:
>> >I use amanda successfully to back up a number of systems
>> > remotely, one via VPN across the Internet. I'm having trouble,
>> > however, with my local system (also the amanda server host)
>> > where it seems to be difficult to get any backups to work. The
>> > box is running Gentoo Linux, xinetd, Amanda version 2.4.4p2,
>> > Linux kernel 2.4.20. A typical report shows:
>> >
>> >FAILURE AND STRANGE DUMP SUMMARY:
>> > vishnu hdb2 lev 0 FAILED [disk hdb2, all estimate failed]
>> > vishnu hdb1 lev 0 FAILED [disk hdb1, all estimate failed]
>> >
>> >... and the backup fails.
>> >
>> >This particular notice is from a test backup on a drive with 2
>> >partitions, one ext2 and the other reiserfs. The dumptype on
>> > both is comp-user or comp-user-tar. All files and directories
>> > on both partitions are mode ugo+r. The amanda xinetd config
>> > contains 'only-from' entries for both the private IP address of
>> > the box and 'localhost'. /etc/amandahosts likewise contains
>> > entries for both the hostname of the box and 'localhost:
>> >
>> >$ cat /etc/amandahosts
>> >localhost amanda
>> >localhost root
>> >[snip snap!]
>> >vishnu.fmp.com amanda
>> >vishnu.fmp.com root
>> >
>> >Does anyone have any ideas what I might try to solve this
>> > problem?
>>
>> First, one should never use localhost, it is not a unique name,
>> and amanda must have unique, no mistaking which machine, names,
>> resolvable in the approriate /etc/hosts file (or by a local dns
>> server),
>
>It's unique on this box.
>
>$ dig +short localhost
>127.0.0.1
It _will_ bite you at some point. Amanda is very very network aware.
Please use the FQDN of the machine even though that might resolve to a
192.168.xx.xx address.
>No ambiguity there.
>
>> and likewise, the ~/.amandahosts file must be similarly
>> treated. I note above that you didn't have the leading dot in the
>> filename you catted above.
>
>/etc/amandahosts doesn't use a leading dot. ~amanda/.amandahosts
> does, and is a symlink to /etc/amandahosts.
Amanda was built as user:
and make install was done as user:
And its perms (~/.amandahosts) are?
>> This may not be your whole problem, but it will remove another
>> often encountered source of recovery time failures. Please read
>> the TOP-TEN-QUESTIONS and FAQ in the tarball.
>
>This isn't a recovery-time issue, it's a backup-time issue. I have
> no problem with either backup or recovery on any of the other
> systems I have for which I use amanda.
>
>The problem is more complex than this. There is _one_ filesystem on
> this box with which amanda has no problems. That's my boot
> partition, which is a small (c.a. 15 megs) ext2 boot partition
> which I _can_ back up. It's both the smallest and least important
> partition on the box, but the fact that I can back it up tells me
> that the problem isn't one of access permissions or name
> resolution. Amanda doesn't care about file permissions,
> apparently, since I can remove read permissions from all files on
> this partition and still back it up.
>
>Amstatus shows:
>
>vishnu:hda2 1 7810k dump done (14:35:22), wait for writing to
> tape vishnu:hda4 0 planner: [disk hda4, all estimate failed]
>
>hda2 succeeds, hda4 fails. Both are set to a dumptype of
> 'nocomp-boot-tar' (not appropriate for hda4, but temporarily
> changing this eliminates a variable). The only thing which
> distinguishes hda2 from any other filesystem on the box is it's
> small size. I tried a test backup on a spare drive, mounted
> temporarily with two nearly identical sets of files on nearly
> identically sized partitions (c.a. 1.5G), one ext2 and one
> reiserfs, and both failed, which eliminates the filesystem type,
> apparently. Amanda has no problem getting estimates on and backup
> up filesystems many times this size on other boxes.
The clues point to serious slowdown someplace.
>I'll take a look for the TOP-TEN-QUESTIONS FAQ and see if it helps,
> but I'm guessing that it probably won't. I'm wondering if this is
> some kind of kernel issue or something equally weird.
The only other item that comes to mind is the etimeout value in your
amanda.conf. Just for testing, multiply it by 10 for tonight, that
big a filesystem may be too slow for the default 5 minutes. Its in
seconds BTW. If that fixes the estimates, you may have to expand the
dtimeout value also.
--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.
|
