DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=UA3fljnQ2MuI5CU6qLA/cagGoJcDDW2Glbci5Dl1tFz8aThD98OVPCtn97T8TVhND6
         K4wmdodVnrXFpmpMwgXUC5dMHipVkVcBvcTvjwOK3eEfaRdAh9UtbwuLDVqZkiv5GZ4J
         Mq4ZTFZUkN+YIPYkLldOg6dtQdt/VzRj0NY00=
Message-ID: <81083a450806251035k285e4e3dga052f041c9e2d94d@mail.gmail.com>
Date: Wed, 25 Jun 2008 23:05:18 +0530
From: "Ashutosh Naik" <ashutosh.naik@gmail.com>
To: "Mike Christie" <michaelc@cs.wisc.edu>
Subject: Re: Kernel Crash when using the open-iscsi initiator on 2.6.25.6
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
       open-iscsi@googlegroups.com
In-Reply-To: <48627851.9010804@cs.wisc.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <81083a450806242236m62754185t3099c06f9f77676@mail.gmail.com>
	 <48627851.9010804@cs.wisc.edu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1900
Lines: 50

On Wed, Jun 25, 2008 at 10:24 PM, Mike Christie <michaelc@cs.wisc.edu> wrote:

>>  connection5:0: ping timeout of 5 secs expired, last rx 4309652882,
>> last ping 4309657882, now 4309662882
>
>
> However, once it happens we should not report it again like is done here.
> There is something weird there. Do you have the iscsid output? Between these
> two reports of pings timing out is there any messages from iscsid about
> reconnecting?

iscsid tried to reconnect but the target died, I think.

>>  connection5:0: detected conn error (1011)
>>  connection5:0: detected conn error (1011)
>>  session5: host reset succeeded
>
>
> And we should not get here. The iscsi driver's scsi command timeout handler
> should prevent the command from firing the scsi eh, because in this case we
> think it is a transport problem.
>
> What version of the iscsi tools are you using? Are they from a distro or
> open-iscsi.org?
>
> Are you running with the iscsi kernel modules from 2.6.25.6, or are you
> using the iscsi modules from the open-iscsi.org website that come with the
> tarball?
>
> Is the kernel a unmodified 2.6.25.6 or does it have some distro patches or
> patches that you have created?

It was an unmodififed 2.6.25.6 kernel, and open-iscsi version 2.0-869.2

>> INFO: task fdisk:5226 blocked for more than 120 seconds.
>
> I think you get this message and what follows, is a result of the above
> problem. While the iscsi initiator is trying to reconnect, IO is queued by
> the scsi layer so fdisk is going to be waiting around until we recover or
> give up.

Yep, but is there any way to close gracefully and avoid the kernel dump?

Thanks
Ashutosh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/