From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alexander Stohr <Alexander.Stohr@gmx.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
matthew@wil.cx, akpm@digeo.com,
Kai Makisara <Kai.Makisara@kolumbus.fi>
Subject: Re: [BUG] Sym. 53c895 fails accessing tape device - kernel 2.9.1-rc1-bk1 trough rc2-bk12
Date: 02 Oct 2004 11:49:17 -0400 [thread overview]
Message-ID: <1096732158.2169.13.camel@mulgrave> (raw)
In-Reply-To: <13842.1096472870@www69.gmx.net>
On Wed, 2004-09-29 at 11:47, Alexander Stohr wrote:
> in the beginning it merely looks like this:
> kernel: st0: Incorrect block size.
I think this is the key to the problem. It looks like some sort of tape
error.
> then it changed slightly to this:
> kernel: sym1:4:0:phase change 6-7 9@37d30f84 resid=6.
> kernel: sym1:4:0:phase change 6-7 9@37d30f84 resid=6.
These are normal messages printed during sym2 negotiation. The way it
does negotiation changed recently, so these became more prevalent
Kai, could you look into this?
When I haul an old DAT tape out of the cupboard and attach it to a
sym1010, it all seems to work until I try to manipulate the block size,
so
dd of=/dev/nst0 if=linux-2.6.8.tar.gz
works just fine ... I can read and write to the tape
dd of=/dev/nst0 if=linux-2.6.8.tar.gz obs=16k
fails with the kernel message
st0: Write not multiple of tape block size.
And then I start to get errors from the tape device.
It looks like the block size setting has been broken somehow.
James
next prev parent reply other threads:[~2004-10-02 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 15:47 [BUG] Sym. 53c895 fails accessing tape device - kernel 2.9.1-rc1-bk1 trough rc2-bk12 Alexander Stohr
2004-10-02 15:49 ` James Bottomley [this message]
2004-10-02 20:25 ` Kai Makisara
2004-10-02 21:50 ` James Bottomley
2004-10-02 22:28 ` James Bottomley
2004-10-03 9:07 ` [BUG] Sym. 53c895 fails accessing tape device - kernel2.9.1-rc1-bk1 " Alexander Stohr
2004-10-03 9:37 ` Kai Makisara
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=1096732158.2169.13.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=Alexander.Stohr@gmx.de \
--cc=Kai.Makisara@kolumbus.fi \
--cc=akpm@digeo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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