From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 7 10:47:18 2009 Return-Path: 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 1D47F106564A for ; Wed, 7 Jan 2009 10:47:18 +0000 (UTC) (envelope-from nglrossi@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id C84E28FC18 for ; Wed, 7 Jan 2009 10:47:17 +0000 (UTC) (envelope-from nglrossi@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so3552392ywe.13 for ; Wed, 07 Jan 2009 02:47:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=OjY+IGB42UPemRHvAI/Jz6fVjX1nwzIbcxR9YylLUGE=; b=xAzmORVv7ZpdsXAmzFGyLDb2ncMposJ5oNn1VK8HLsZXlsXu0BHKXofWEZvd/ljTwo ISATHBX+Cvm4TisHX5WpxkQWoeo50Ct/zSAcdqmhk0ZSRJ39phddp/YfhrabaQALXYGe jb7hwoo+tH1UiqZ2THeMMiDD3iDc+jkmvymn8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=T2MiGBaj7dFN2QVpJd+XnPw2cusi1gWQzOLzCW1cUp51mOT8lY/o2MIxeB8gY0La4Q 5jbUQhnrg6Pp08tGOHHnaODwRzrg7kdAiIyEwfqG0miLl8N/Ulqd3bZ9ezuKe97Mjl5s i5ljHPRf4To01ASVBI8SWIxLQYmoXyJTopHtU= Received: by 10.100.127.15 with SMTP id z15mr12318808anc.10.1231325237123; Wed, 07 Jan 2009 02:47:17 -0800 (PST) Received: by 10.100.136.13 with HTTP; Wed, 7 Jan 2009 02:47:17 -0800 (PST) Message-ID: <6c1e076a0901070247l7c006efajda8fddee84c337a@mail.gmail.com> Date: Wed, 7 Jan 2009 11:47:17 +0100 From: Angelo To: "Danny Braniss" , freebsd-scsi@freebsd.org In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 10:47:18 -0000 On Wed, Jan 7, 2009 at 10:33 AM, Danny Braniss wrote: > > 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" > > > > Hi Danny, thanks for your reply. when the target comes back it is reconnected properly by the initiator. The usage of iscsi I had in mind was an initiator connecting to two targets and using the two devices as parts of a raid 1 array. I was expecting that a failure on one of the disks (network down, target machine down) would be eventually detected and the raid turned to degraded but still usable. What happens now to me is that the whole raid device gets unusable for all the time the target is down. As I said before I am just experimenting. I don't know how other implementations of iscsi initiator work and maybe my idea is just insane :) Thanks, Angelo