On Wednesday 17 December 2003 06:20, Dan L. Ostrom wrote:
>Gene,
> Well, this did not change anything.
>
> I now have version 1.13.25 of tar and the latest version of
> amanda (patched).
>
> It still fails with the *disk offline* error. The log file
> shows that amanda is
>not getting the size parameter from the sendsize module:
>
>====================================================================
>======== =========
>tidi05:/tmp/amanda> more sendsize.20031217020109.debug
>sendsize: debug 1 pid 27259 ruid 2 euid 2: start at Wed Dec 17
> 02:01:09 2003 sendsize: version 2.4.4p1
>sendsize[27262]: time 0.017: calculating for amname
>'/data/tidi/BACKUP_LOGS', di
>rname '/data/tidi/BACKUP_LOGS', spindle -1
>sendsize[27262]: time 0.018: getting size via gnutar for
>/data/tidi/BACKUP_LOGS
>level 0
>sendsize[27259]: time 0.019: waiting for any estimate child
>sendsize[27262]: time 0.054: spawning /usr/local/libexec/runtar in
> pipeline sendsize[27262]: argument list: /opt/bin/tar --create
> --file /dev/null --directo
>ry /data/tidi/BACKUP_LOGS --listed-incremental
>/usr/local/var/amanda/gnutar-list
>s/tidi05_data_tidi_BACKUP_LOGS_0.new --sparse --ignore-failed-re
>ad --totals --exclude-from
>/tmp/amanda/sendsize._data_tidi_BACKUP__LOGS.20031217
>020109.exclude .
This next sequence looks a bit suspect to me. Do you need to adjust
the perms on that client? AIUI, runtar should do an suid root, and
if already root, it could fail. But I'll leave the final
determination to the experts in bigger systems.
>sendsize[27262]: time 0.090: runtar: error [must be invoked by root]
>sendsize[27262]: time 0.092:
>sendsize[27262]: time 0.093: .....
>sendsize[27262]: estimate time for /data/tidi/BACKUP_LOGS level 0:
> 0.039 sendsize[27262]: no size line match in /opt/bin/tar output
> for "/data/tidi/BACKU
>P_LOGS"
>sendsize[27262]: .....
>sendsize[27262]: estimate size for /data/tidi/BACKUP_LOGS level 0:
> -1 KB sendsize[27262]: time 0.093: waiting for /opt/bin/tar
>"/data/tidi/BACKUP_LOGS" c
>hild
>sendsize[27262]: time 0.093: after /opt/bin/tar
> "/data/tidi/BACKUP_LOGS" wait sendsize[27262]: time 0.103: done
> with amname '/data/tidi/BACKUP_LOGS', dirname
>'/data/tidi/BACKUP_LOGS', spindle -1
>sendsize[27259]: time 0.104: child 27262 terminated normally
>sendsize: time 0.104: pid 27259 finish time Wed Dec 17 02:01:09 2003
>====================================================================
>======== =====================
> So I guess some more investigation is needed here.
>
>>X-Authentication-Warning: guinness.omniscient.com: majordom set
>> sender to owner-amanda-users AT amanda DOT org using -f
>>X-Sender: dostrom AT d.imap.itd.umich DOT edu
>>X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
>>Date: Tue, 16 Dec 2003 19:31:40 -0500
>>To: gene.heskett AT verizon DOT net
>
From: "Dan L. Ostrom" <dostrom AT umich DOT edu>
>
>>Subject: Re: gnutar version -- exactly 1.13.25 or just 1.13.25 and
>> above?
>>Cc: Paul Bijnens <paul.bijnens AT xplanation DOT com>,
>> Mark_Conty AT cargill DOT com, amanda-users AT amanda DOT org
>>Sender: owner-amanda-users AT amanda DOT org
>>
>>Gene,
>> Thanks, our version of tar here is 1.13. Looking into
>> upgrading it.
>>
>> I am currently running amanda-2.4.4p1. I'll check into the
>>patches available.
>>
>> I'll post to the group the success/failure of all of this.
>>
>>At 07:23 PM 12/16/2003, Gene Heskett wrote:
>>>On Tuesday 16 December 2003 17:38, Paul Bijnens wrote:
>>> >Mark_Conty AT cargill DOT com wrote:
>>> >> Question: Is it to be understood that versions of gnutar
>>> >> _greater_ than 1.13.25 are also incompatible? Or is it
>>> >> implied that those are also valid & acceptable for use with
>>> >> Amanda?
>>> >>
>>> >> I ask because I'm seeing the same problem as is Mr. Kato, only
>>> >> I'm on an HP-UX server, running gnutar 1.13.90 and Amanda
>>> >> 2.4.4p1. chg-scsi is dumping to one of four tape drives in a
>>> >> 4/48 DLT library.
>>> >
>>> >Wow, tar seems to be awake again.
>>> >Download 1.13.92, compiled, tested.
>>> >
>>> >Not good, at least not without some patches to amanda...
>>> >
>>> >1. Every backup now generates a message
>>> >
>>> > tar: Removing leading `./' from member names
>>> >
>>> > Amanda flags this line for each DLE as "strange".
>>> >
>>> >2. by removing the leading `./' now amrecover has trouble
>>> > and does not find anything back in the index.
>>>
>>>I got an even better question Paul. Why not file a bug report
>>> against the new version? And see what sort of a reason they give
>>> for breaking all semblences of backwards compatibility.
>>>I haven't tried it personally of course, and it appears thats my
>>> clue to leave that sleeping dog lie quietly.
>>>
>>>--
>>>Cheers, Gene
>>>AMD K6-III@500mhz 320M
>>>Athlon1600XP@1400mhz 512M
>>>99.22% setiathome rank, not too shabby for a WV hillbilly
>>>Yahoo.com attornies please note, additions to this message
>>>by Gene Heskett are:
>>>Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
>>
>>############################################################
>># Dan L. Ostrom | IT Contract Services #
>># Systems Administrator III | (734) 647-5664 (voice) #
>># University of Michigan | (734) 670-4001 pager) #
>># Ann Arbor Michigan | (734) 763-4050 (fax) #
>># 48109 | #
>>############################################################
>
>############################################################
># Dan L. Ostrom | IT Contract Services #
># Systems Administrator III | (734) 647-5664 (voice) #
># University of Michigan | (734) 670-4001 pager) #
># Ann Arbor Michigan | (734) 763-4050 (fax) #
># 48109 | #
>############################################################
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
|
