From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: jelledejong@powercraft.nl
Cc: stgt@vger.kernel.org
Subject: Re: what do these abort_cmd(1324) and abort_task_set(1348) messages in the logs mean?
Date: Thu, 10 Jul 2014 09:14:35 +0900 (JST) [thread overview]
Message-ID: <20140710.091435.1305564732068198316.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <53BD52AE.6030206@powercraft.nl>
On Wed, 09 Jul 2014 16:33:18 +0200
Jelle de Jong <jelledejong@powercraft.nl> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dear FUJITA,
>
> On 09/07/14 16:16, FUJITA Tomonori wrote:
>> On Wed, 09 Jul 2014 16:15:42 +0200 Jelle de Jong
>> <jelledejong@powercraft.nl> wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>
>>> Dear FUJITA,
>>>
>>> On 27/06/14 13:57, FUJITA Tomonori wrote:
>>>> On Tue, 17 Jun 2014 12:24:07 +0200 Jelle de Jong
>>>> <jelledejong@powercraft.nl> wrote:
>>>>
>>>>> What do these tgtd messages mean? Is something wrong? Why
>>>>> are they there?
>>>>>
>>>>> http://paste.debian.net/105427/
>>>>
>>>> A SCSI command was aborted for some reason (e.g. the time-out
>>>> of a SCSI command due to the overloaded iscsi target).
>>>>
>>>> The cricial bug about this was fixed in 1.0.48. I would
>>>> recommend you to update tgt if you use the older version.
>>>
>>> I upgraded to version 1.0.48 about a week ago for further
>>> testing, I also added a complete new network path, with new
>>> network cards and direct connections, but I keep getting these
>>> same errors:
>>>
>>> http://paste.debian.net/108884/
>>>
>>> Is this a bug in tgtd? Is there some tgtd option or environment
>>> variable that I can set to get more information.
>>
>> It's not a bug. It's just a message tells that SCSI command
>> time-out happens for some reasons.
>
> Can you help me with some more information to solve the problems?
>
> Is this SCSI command time-out something that happened on the target
> server with the storage, my storage is having a hard time with high
> latencies, but I am not having any hardware warnings/errors. Or is
> this related to the iSCSI client servers as well?
Without any hardware errors, a target could takes long time to execute
SCSI commands (e.g., simply overloaded). It depends on your
environment.
You could set a longer value for SCSI command time-out on the client
side.
prev parent reply other threads:[~2014-07-10 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 10:24 what do these abort_cmd(1324) and abort_task_set(1348) messages in the logs mean? Jelle de Jong
2014-06-27 10:50 ` Jelle de Jong
2014-06-27 11:57 ` FUJITA Tomonori
2014-07-09 14:15 ` Jelle de Jong
2014-07-09 14:16 ` FUJITA Tomonori
2014-07-09 14:33 ` Jelle de Jong
2014-07-10 0:14 ` FUJITA Tomonori [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=20140710.091435.1305564732068198316.fujita.tomonori@lab.ntt.co.jp \
--to=fujita.tomonori@lab.ntt.co.jp \
--cc=jelledejong@powercraft.nl \
--cc=stgt@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).