From: Andrew Morton <akpm@osdl.org>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
bergenia@pair.com
Subject: Re: Fw: [Bugme-new] [Bug 7610] New: sense key error when sending even number of bytes to /dev/st0
Date: Sat, 2 Dec 2006 11:16:28 -0800 [thread overview]
Message-ID: <20061202111628.3fa148bc.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612021717040.5255@kai.makisara.local>
(Originator and bugzilla added to cc)
On Sat, 2 Dec 2006 17:27:20 +0200 (EET)
Kai Makisara <Kai.Makisara@kolumbus.fi> wrote:
> On Fri, 1 Dec 2006, Andrew Morton wrote:
>
> >
> >
> > Begin forwarded message:
> >
> > Date: Fri, 1 Dec 2006 08:40:16 -0800
> > From: bugme-daemon@bugzilla.kernel.org
> > To: bugme-new@lists.osdl.org
> > Subject: [Bugme-new] [Bug 7610] New: sense key error when sending even number of bytes to /dev/st0
> >
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=7610
> >
> > Summary: sense key error when sending even number of bytes to
> > /dev/st0
> > Kernel Version: 2.6.19
> > Status: NEW
> > Severity: normal
> > Owner: other_modules@kernel-bugs.osdl.org
> > Submitter: bergenia@pair.com
> >
> >
> > Most recent kernel where this bug did *NOT* occur: unknown
> > Distribution: Debian, but using kernel from kernel.org
> > Hardware Environment: Dell Poweredge 2800 Xeon, Quantum DLT VS160 tape drive,
> > scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
> > <Adaptec 3960D Ultra160 SCSI adapter>
> > aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
> > Software Environment:
> > Gnu C 3.3.5
> > Gnu make 3.80
> > binutils 2.15
> > util-linux 2.12p
> > mount 2.12p
> > module-init-tools 3.2.2
> > e2fsprogs 1.37
> > nfs-utils 1.0.6
> > Linux C Library 2.3.6
> > Dynamic linker (ldd) 2.3.6
> > Procps 3.2.1
> > Net-tools 1.60
> > Console-tools 0.2.3
> > Sh-utils 5.2.1
> > udev 088
> > Modules Loaded st parport_pc parport
> >
> > Problem Description:
> > When sending an even number of bytes to /dev/st0, I get the following error in
> > /var/log/kernel:
> >
> > Nov 30 16:13:47 mugsy kernel: st0: Current: sense key: Illegal Request
> > Nov 30 16:13:47 mugsy kernel: Additional sense: Invalid field in cdb
> >
> > Steps to reproduce:
> > this will write to the tape:
> >
> > echo "A" > /dev/st0
> > echo "ABC" > /dev/st0
> >
> > this will not write to the tape and will produce the kernel error:
> >
> > echo "AB" > /dev/st0
> > echo "ABCD" > /dev/st0
> >
> I think this is not a bug but a user error.
>
> Firstly, the report should say that writing odd number of bytes does not
> work (echo adds newline to the data).
>
> The reason for the problem is probably that the drive in question does not
> support writing blocks with odd number of bytes. I just tested the echo
> commands with my drive and all echos succeeded (kernel 2.6.19).
>
> --
> Kai
prev parent reply other threads:[~2006-12-02 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 19:29 Fw: [Bugme-new] [Bug 7610] New: sense key error when sending even number of bytes to /dev/st0 Andrew Morton
2006-12-02 15:27 ` Kai Makisara
2006-12-02 19:16 ` Andrew Morton [this message]
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=20061202111628.3fa148bc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Kai.Makisara@kolumbus.fi \
--cc=bergenia@pair.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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