>Problem with this is obtaining a definitive PROOF. Welcome to my world.
>you do the amanda process, and you notice that the tape is not spinning, >even though you are in the sendbackup phase. ... It might not be spinning if you have enough holding disk that the image is going there first. However I gather that's not the case with your system, so this means taper is not getting any data from the client. Moving further back in the chain ... >You notice that the ethernet switch is not blinking. ... Which matches the above and also says the client is not even trying. So we continue to move on back ... >You can also notice the task(s) that are running. ... So it's not that they just died, so now we move forward a bit from the far end ... >You also notice that the disk controller light is light. Are you saying the disk is "busy"? If so, then it's likely tar (or the OS) is grinding away but not generating any data into the pipeline to Amanda (sendbackup), as you've already pretty well guessed. So this is purely a tar (or OS or hardware) issue. If you did exactly the same thing by hand that Amanda is asking tar to do, it would act the same way. What's going on here is totally independent of Amanda. Next would be to run truss or a debugger on tar and find out what it's up to, then talk to those folks. >You can make some general conclusions, like gee the reason i up'ed the >destimate value from 30min to 6hours is due to what is occuring now. ... You upped that value as a workaround for something very, very odd/bad with the way tar is working on your system. >/gat John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
