From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 13 11:12:47 2010 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 EAC311065672 for ; Wed, 13 Jan 2010 11:12:47 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8C10E8FC16 for ; Wed, 13 Jan 2010 11:12:47 +0000 (UTC) Received: from HPQuadro64.dmpriest.net.uk (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/Kp) with ESMTP id o0DAwjsx035623 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Jan 2010 10:58:45 GMT Date: Wed, 13 Jan 2010 10:58:26 +0000 From: Karl Pielorz To: freebsd-scsi@freebsd.org Message-ID: <071FB5A0A2DC2EFA265933DE@HPQuadro64.dmpriest.net.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Starting out in iSCSI - recovery questions / options from target vanishing... 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, 13 Jan 2010 11:12:48 -0000 Hi, I've been looking at setting up iSCSI on my home network. I have a windows machine, which I've installed iSCSI target software on, and set it up. I'm using FreeBSD 7.2-STABLE - and I've setup iSCSI as an initiator on that. At the end of the day, I get the following logged when I've finished setting it up: " Jan 12 20:25:30 test kernel: da0 at iscsi0 bus 0 target 0 lun 0 Jan 12 20:25:30 test kernel: da0: Fixed Direct Access SCSI-4 device Jan 12 20:26:21 test kernel: GEOM_LABEL: Label for provider da0s1 is ufsid/4b4cdaed5db746bf. " I can label, partition, format and mount da0 - and everything works fine, which looks pretty successful. Until I 'break the connection' - either by restarting the windows iSCSI target, or pulling the network cable. Whatever was in progress on da0 expectedly freezes. However, when the connection is available again - nothing seems to re-attach, continue, or error. I'd guess I may be being optimistic if I expected it to re-attach, and continue without error - but is there any way of either avoiding the freeze (or raining in the timeout) - or forcing things to try to reconnect? I don't mind getting errors, or trashing the iSCSI drive (it's only used for shifting backups on to large drives on the windows machine) - but as it is, the only way to recover is to restart the FreeBSD box. If someone can point me in the right direction, or explain what's "meant to happen" that'd be great, Thanks, -Karl