On Wed, 09 Jul 2014 16:33:18 +0200 Jelle de Jong <jelledejong@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
