On Fri, 3 Nov 2000 at 6:30pm, John R. Jackson wrote
> >Curiously, each of the three times, the tape error occurs just under
> >3 minutes into the amdump run. Of course, the amflush the next day works
> >just fine, taking almost an hour to do so. ...
>
> The only thing that pops to mind is a SCSI problem. Is your holding
> disk on the same bus as the drives? That would be the main difference
> between amdump and amflush -- during amdump one or more processes are
> writing into the holding disk at the same time taper is dragging stuff
> out and writing it to tape. A lot more disk and controller activity.
>
Yeah, SCSI issues would seem to be the likely culprit. The tape drive is
actually on a different bus than the hard drives, though. I *was* having
some issues with scsi0, but those seem to have gone away (knock on
wood) with a hard drive replacement. scsi1 (the tape and a CD-R) was
working fine before and after the switch, then started acting up.
> Check the cable. Check the termination. Move the devices (if possible)
> to other buses.
>
I actually swapped the tape drive with another (identical) one I had
hooked to a different machine. The cable and termination got checked, of
course, in the process. We'll see what happens tonight.
Now, I did give scsi0 some blood during the hard drive swap. I'm thinking
scsi1 got jealous and needs its taste...
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
