From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
dvyukov@google.com, hare@suse.com, hch@lst.de,
martin.petersen@oracle.com
Subject: Re: [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control
Date: Wed, 19 Jul 2017 03:13:34 -0500 [thread overview]
Message-ID: <ufazic0974h.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <20170719070335.GC4151@linux-x5ow.site> (Johannes Thumshirn's message of "Wed, 19 Jul 2017 09:03:35 +0200")
>>>>> "JT" == Johannes Thumshirn <jthumshirn@suse.de> writes:
JT> Can you please apply this debugging patch, so I can see what's going
JT> on.
Sure, no problem.
I generally run "mtx -f /dev/sg7 status" first just to make sure the
library is there; this has always worked as expected. With the debug
patch applied, this is sent to the console:
[ 33.933422] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 56
[ 33.940526] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 136
[ 33.982429] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 4240
[ 34.569986] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 4240
[ 34.623898] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 4240
Then running "mtx -f /dev/sg7 next 0" gives this as stdout/err:
Unloading drive 0 into Storage Element 46...mtx: Request Sense: Long
Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=0 (Unknown?!)
mtx: Request Sense: Sense Key=No Sense
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 00
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
MOVE MEDIUM from Element Address 1 to 1046 Failed
And this to the console:
[ 45.552524] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 56
[ 45.559626] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 136
[ 45.603544] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 4240
[ 46.204614] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 4240
[ 46.258463] sg_is_valid_dxfer: dxfer_direction: -3, dxfer_len: 4240
[ 46.304530] sg_is_valid_dxfer: dxfer_direction: -2, dxfer_len: 0
Would you also want to see the output from that patch applied to a
functioning kernel?
- J<
next prev parent reply other threads:[~2017-07-19 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 0:44 [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control Jason L Tibbitts III
2017-07-18 7:37 ` Johannes Thumshirn
2017-07-18 16:53 ` Jason L Tibbitts III
2017-07-18 17:33 ` Jason L Tibbitts III
2017-07-19 7:03 ` Johannes Thumshirn
2017-07-19 8:13 ` Jason L Tibbitts III [this message]
2017-07-19 8:36 ` Johannes Thumshirn
2017-07-21 16:43 ` Johannes Thumshirn
2017-07-21 19:23 ` Jason L Tibbitts III
2017-07-25 7:18 ` Johannes Thumshirn
2017-07-25 18:25 ` Jason L Tibbitts III
2017-07-26 7:39 ` Johannes Thumshirn
2017-07-26 20:19 ` Jason L Tibbitts III
2017-07-25 19:09 ` Douglas Gilbert
2017-07-26 7:22 ` Johannes Thumshirn
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=ufazic0974h.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--cc=dvyukov@google.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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