From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Brooks <arb@sat.dundee.ac.uk>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Tagged overlapped commands
Date: Sun, 07 Dec 2014 23:02:58 -0800 [thread overview]
Message-ID: <1418022178.21408.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHOfOo3D9iXmesTGq-tf397WucY95D7kqZ7rtKshWyzBa1U9ow@mail.gmail.com>
Adding linux-scsi back to cc. Please don't drop because others may be
interested and it allows search engines to find the answer.
On Fri, 2014-12-05 at 13:09 +0000, Andrew Brooks wrote:
> On 4 December 2014 at 16:17, James Bottomley <
> James.Bottomley@hansenpartnership.com> wrote:
>
> > The error message likely means that the tape device had more than one
> > command outstanding at once (i.e. one command was sent while the current
> > command was still pending). It could also mean that a tag got re-used
> > (same tag issued while command with that tag was outstanding) but for a
> > tape I think the former is more likely. Is the queue depth set to one
> > for the device?
> >
>
> Thanks for your reply, How can I configure the queue depth?
it should be under
/sys/class/scsi_device/<dev>/device/queue_depth
you can (as root) echo a value in there to change the depth.
James
next prev parent reply other threads:[~2014-12-08 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 12:24 Tagged overlapped commands Andrew Brooks
2014-12-04 15:59 ` Andrew Brooks
2014-12-04 16:17 ` James Bottomley
[not found] ` <CAHOfOo3D9iXmesTGq-tf397WucY95D7kqZ7rtKshWyzBa1U9ow@mail.gmail.com>
2014-12-08 7:02 ` James Bottomley [this message]
2014-12-16 10:23 ` Andrew Brooks
2014-12-18 0:16 ` Elliott, Robert (Server Storage)
[not found] <CAHOfOo25V9Qqv=K7n5DnwDyN6TGBEzikMzhZ6OhF_2=+wG=bMg@mail.gmail.com>
2014-12-17 17:18 ` Andrew Brooks
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=1418022178.21408.5.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=arb@sat.dundee.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.