Okay, I just ran amdump manually, with much the same result (one large partition results in an end-of-tape message in the Amanda report, but it looks like something else is really going on).
Here's what I found in /var/log/messages. I believe "sense key" means the system (st()?) asked the drive what was up and got a response... but I don't really understand the response: Jun 26 16:11:34 agrippa kernel: st0: Error with sense data: Info fld=0x0, Deferred st09:00: sense key Medium Error Jun 26 16:11:34 agrippa kernel: Additional sense indicates Logical unit communication time-out Jun 26 16:11:34 agrippa kernel: st0: Error with sense data: Info fld=0x0, Deferred st09:00: sense key Medium Error Jun 26 16:11:34 agrippa kernel: Additional sense indicates Logical unit communication time-out Jun 26 16:11:34 agrippa kernel: st0: Error on write filemark. Jun 26 16:11:34 agrippa sendbackup[31899]: index tee cannot write [Connection reset by peer] This would seem to indicate that scsi tape 0 is messing up. Which makes sense since it's the only one I have. However, I am pointing the whole amanda operation at /dev/nst0 and not /dev/st0, since nst0 (I believe) is the non-rewinding device 'connection'. Am I wrong to assume that? Could there be some other parameter that I've screwed up? :) Here's the relevant line from the Notes section of the repoort, in case it helps... taper: tape DailySet1-14 kb 5070592 fm 6 writing file: Input/output error Is there documentation on what the fields are in this note? It /appears/ to mean that it wrote just about 5 GB... does the fm 6 mean 'file mark 6' maybe? Last time it was fm 4, with about 300 MB more written. Once again, thanks a million for your help so far, guys. I really appreciate it. Jesse On Wed, 26 Jun 2002 10:51:43 -0400 (EDT) "Joshua Baker-LePain" <[EMAIL PROTECTED]> wrote: > On Wed, 26 Jun 2002 at 10:13am, Jesse Griffis wrote > > > I am getting an odd end-of-tape error on every tape, every time I try > > to write a very large file. Below is the Amanda report for the last > > attempt I tried. I'm chopping out some of the extraneous detail (the > > > > > These dumps were to tape DailySet1-17. > > *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]]. > > Note that here amanda is just telling you what the OS told it. For more > detail on exactly what sort of I/O error occurred, look in > /var/log/messages. > > > Tape Time (hrs:min) 0:12 0:12 0:00 > > Tape Size (meg) 4590.4 4590.4 0.0 > > Tape Used (%) 7.7 7.7 0.0 > > Filesystems Taped 3 3 0 > > Avg Tp Write Rate (k/s) 6776.7 6776.7 -- > > In here there should be a NOTES section. That will tell you *exactly* how > > much data got to tape before the I/O error. As Jon mentioned, make sure > that you're not using hardware compressions, as you are using software > compression. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > > > > >
