From: rct@gherkin.frus.com (Bob Tracy)
To: linux-kernel@vger.kernel.org
Cc: axboe@suse.de, Kai.Makisara@metla.fi
Subject: 2.5.72: SCSI tape error handling
Date: Thu, 19 Jun 2003 16:36:35 -0500 (CDT) [thread overview]
Message-ID: <20030619213635.AD2874F01@gherkin.frus.com> (raw)
I was trying to do the responsible thing and back up my system today
(for the first time in too many weeks :-)), and got the following
errors in syslog about 15 minutes into the process:
Jun 19 09:55:04 gherkin kernel: st0: Error with sense data: Info fld=0x3ba, Deferred stst0: sense key Medium Error
Jun 19 09:55:04 gherkin kernel: Additional sense: Write append position error
Jun 19 09:55:04 gherkin kernel: st0: Error with sense data: Current stst0: sense key Medium Error
Jun 19 09:55:04 gherkin kernel: Additional sense: Write append position error
Jun 19 09:55:04 gherkin kernel: st0: Error with sense data: Current stst0: sense key Medium Error
Jun 19 09:55:04 gherkin kernel: Additional sense: Write append position error
(... ad infinitum for the next three hours -- backup was unattended.
There were no error messages of any kind on the console.)
I'm going to ASSume that cpio would have done something appropriate if
the underlying write() call had returned some kind of error. The fact
that write() is evidently NOT returning an error is a problem. For me,
it's a show-stopper. I can handle bad tapes if the userland side of
things will report there's a problem.
st0 is an Exabyte 8mm tape drive. SCSI adapter is an Adaptec 2930U2
using the new aic7xxx driver (as included with the 2.5.72 kernel).
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2003-06-19 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 21:36 Bob Tracy [this message]
2003-06-20 12:11 ` Kai Makisara
2003-06-20 13:08 ` Bob Tracy
2003-06-20 17:49 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030619213635.AD2874F01@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=Kai.Makisara@metla.fi \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®