[stgt] what do these abort_cmd(1324) and abort_task_set(1348) messages in the logs mean?
Jelle de Jong
jelledejong at powercraft.nl
Wed Jul 9 16:15:42 CEST 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 27/06/14 13:57, FUJITA Tomonori wrote:
> On Tue, 17 Jun 2014 12:24:07 +0200 Jelle de Jong
> <jelledejong at powercraft.nl> wrote:
>> What do these tgtd messages mean? Is something wrong? Why are
>> they there?
> 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:
Is this a bug in tgtd? Is there some tgtd option or environment
variable that I can set to get more information.
This system have been stable for more then a year with very old
versions 1.0.17 of tgt but these versions didn't shutdown the target
very reliable when using pacemaker and corosync, making it hang (I
didn't experience this with the newer versions).
Jelle de Jong
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the stgt