From owner-freebsd-firewire@FreeBSD.ORG Thu Dec 16 02:35:16 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A38616A4CE for ; Thu, 16 Dec 2004 02:35:16 +0000 (GMT) Received: from teryx.bobdbob.com (w178.z067105181.was-dc.dsl.cnc.net [67.105.181.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA35643D58 for ; Thu, 16 Dec 2004 02:35:11 +0000 (GMT) (envelope-from protius@teryx.bobdbob.com) Received: from teryx.bobdbob.com (localhost [127.0.0.1]) by teryx.bobdbob.com (8.12.10/8.12.10) with ESMTP id iBG2YwLU071559; Wed, 15 Dec 2004 21:34:58 -0500 (EST) (envelope-from protius@teryx.bobdbob.com) Received: (from protius@localhost) by teryx.bobdbob.com (8.12.10/8.12.10/Submit) id iBG2YqFi071556; Wed, 15 Dec 2004 21:34:52 -0500 (EST) (envelope-from protius) Date: Wed, 15 Dec 2004 21:34:52 -0500 (EST) From: Protius Message-Id: <200412160234.iBG2YqFi071556@teryx.bobdbob.com> To: freebsd-firewire@freebsd.org, tcpdump23@hotmail.com In-Reply-To: Subject: Re: Firewire SAN X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: protius@bobdbob.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 02:35:16 -0000 >I'm considering taking up the idea of firewire-based SAN as a graduation >project. As I was looking at T13 (http://www.t13.org) and have found a >document about firewire-ATA attachment, so I was wondering if anybody out >there is already working on it as an opensource project (I know commercial >implementations of this idea exist). >More importantly, I was seeking the insight of the expertise in this mailing >list regarding the viability of this project and the difficulty (or lack >thereof) associated with it. Its not firewire <-> ATA, but you may want to look at scsi_target (in /usr/share/examples/scsi_target) and sbp_targ(4). (On a FreeBSD 5.3 box) There is a bug in scsi_target. I see it most easily when trying to write more than one block at a time onto a scsi_target. What happens is that there is a completed io queue (cmplt_io), and the same node gets inserted into it more than once, such that the TAILQ_FOREACH_REVERSE loop at line 697 of scsi_target.c (version 1.16) never exits. I havn't had time (day job, etc.) to finish hunting down exactly whats going on... But theres a heads up, if you look at it. -- -Tommy KE4ILZ "Microsoft wants shareholders. Open source programmers tjohnson@bobdbob.com "want the damn thing to work." - Cliff Sarginson Bottom posting makes you more readable. http://www.caliburn.nl/topposting.html