From owner-freebsd-scsi@FreeBSD.ORG  Wed Jan  7 09:33:27 2009
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F33C1106566C
	for <freebsd-scsi@freebsd.org>; Wed,  7 Jan 2009 09:33:26 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
	by mx1.freebsd.org (Postfix) with ESMTP id AE17E8FC13
	for <freebsd-scsi@freebsd.org>; Wed,  7 Jan 2009 09:33:26 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by kabab.cs.huji.ac.il with esmtp
	id 1LKUmz-000O18-Kp; Wed, 07 Jan 2009 11:33:25 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: Angelo <nglrossi@gmail.com>
In-reply-to: Your message of Tue, 6 Jan 2009 18:38:27 +0100 .
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 07 Jan 2009 11:33:25 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1LKUmz-000O18-Kp@kabab.cs.huji.ac.il>
Cc: freebsd-scsi@freebsd.org
Subject: Re: iscsi client hangs performing I/O on a dead target 
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2009 09:33:27 -0000

> Hi,
> 
> I'm experimenting on iscsi; both the target and the initiator are vmware
> virtual machines and are running 7.0-RELEASE.
> So far everything works fine except that the client hangs forever (state is
> PHYSWR) if it is accessing (dd if=/dev/zero of=/dev/da0) the device while it
> "dies" (shutdown of the target machine).
> 
what happens when you bring back the target?

> Is this the expected behaviour?
> 
yes. 
but maybe it can be 'fixed', I'm concidering adding some kind of timeout
flag/option.

> I would like to be able to configure a timeout so the command that is trying
> to access the unavailable device fails and I can handle the problem but I
> can't find anything in iscontrol man pages.
> 
> Thanks,
> Angelo
> _______________________________________________
> freebsd-scsi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"
>