>> This would be a more accurate test:
>> 
>>   dump 0sf 1048576 - /dev/sda5 | (restore -tvf - ; cat > /dev/null)
>
>Suprisingly that ran fine:

Not terribly surprising, but it shows the dump -> restore pipeline is
not the problem.  Now try this:

  /sbin/dump 0sf 1048576 - /dev/sda5 | /bin/gzip -dc | cat > /dev/null

(the extra pipe to cat on the end is to make sure gzip doesn't do any
extraneous optimization -- tar will essentially do nothing if its output
file is /dev/null, for instance).

>I thought the compress getting signal 24 was from the dump returning
>signal 3.  ...

It's the other way around (dump gets the signal 3 because gzip got
the 24).

What's in a sendbackup*debug file corresponding to one of these errors?

>...  I've got working large
>partitions on some other systems - including the tape host:

Are those other systems with large partitions the same type of OS as
the problem client?

>> > runtar: error [must be invoked by operator]
>> ...
>My config.status file on the troublesome client says:
>
># ./configure  --prefix=/usr/local/pkg/amanda-2.4.2p2 --with-user=backup --wit
>h-config=hmcis --with-group=sys

That may be what it says (--with-user=backup), but it's not what's built
into the runtar binary.  The binary is running as though you had said
--with-user=operator.

Take a look at the modification time of amadmin and runtar on that client.
If they are close to the same (i.e. they were built and installed
together), what does "amadmin xx version | grep CLIENT_LOGIN" have to
say when run on the client?  What about "grep CLIENT_LOGIN" in one of
your /tmp/amanda/amandad*debug files?

If you decide to rebuild for this client, make sure you do a "make
distclean" (or "rm config.cache") before so old build information is
not left laying around.

>Do I have to use the
>same user on both server and client if I'm using gnutar?

No.  The only rule is that you have to run Amanda on a machine (client
or server) as the same user you built into the binaries (--with-user).

>  [EMAIL PROTECTED]

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Reply via email to