John,
Still going through the amdump file I sent you and finding new things each
time I do. If you go to the end of the file at the point where it starts
doing the first of the backups that failed, for some reason it starts
backing directly to tape. There doesn't appear to be any reason that I can
see for it to do that. The ONLY backup that was defined to go direct to tape
is localhost:/data1.
markh
-----Original Message-----
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 5:16 PM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help figuring out why these don't complete
>index tee cannot write [Broken pipe]
>...
>Where does the tee come into play so I can tell what application failed?
...
The tee is caused by having indexing turned on. The dumper terminated
for some reason and there was nothing on the other end of that file
descriptor to write to any more, which caused a "Broken pipe" error.
This is just a symptom, not a real problem. For instance, it is perfectly
normaly when writing direct to tape and the tape fills.
>I eliminated the three partitions from the disk list that kept giving the
>"dumper messing up" messages, just to get them out of the picture so that I
>might be able to get the rest of it backed up. I am still getting tons of
>fails with no apparent reason for it. ...
Look at the output. You're still getting the "messed up" messages.
I asked before if you had any core files in /tmp/amanda. Do you? If you
do, please run gdb (or whatever) on them and post the stack traceback.
> markh
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
