From owner-cvs-all@FreeBSD.ORG Tue Oct 10 23:17:05 2006 Return-Path: X-Original-To: cvs-all@freebsd.org Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3647716A40F; Tue, 10 Oct 2006 23:17:05 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1DC743D73; Tue, 10 Oct 2006 23:17:04 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 10 Oct 2006 16:14:05 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id k9ANH4vg019001; Tue, 10 Oct 2006 16:17:04 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id k9ANH46Z019000; Tue, 10 Oct 2006 16:17:04 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200610102317.k9ANH46Z019000@ambrisko.com> In-Reply-To: <20061010160707.Q27309@demos.bsdclusters.com> To: Kip Macy Date: Tue, 10 Oct 2006 16:17:04 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: src-committers@FreeBSD.org, Doug Ambrisko , Kip Macy , cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, Ceri Davies , John Birrell Subject: Re: cvs commit: src/sys/conf Makefile.sun4v files.sun4v options.sun4v src/sys/sun4v/compile .cvsignore src/sys/sun4v/conf DEFAULTS GENERIC GENERIC.hints MAC Makefile NOTES src/sys/sun4v/include _bus.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 23:17:05 -0000 Kip Macy writes: | | The interface is not the same - can one buy an adapter? True that technically the interface is not the same. The SAS connector spans the power supply and data port. SATA has separate data and power. However, the mechanical spacing is the same except the SAS drive does not have the gap to fit a separate power cable and separate data cable. I've stuck several SATA drives in a SAS backplane enclosure and Adaptec fan out cable. The mechanical interface precludes a SAS driver plugged into a SATA controller but the converse is not true. Do you have a SATA drive to try? I've even mixed a SAS and SATA drives on the same controller at the same time. I know a few people using SATA on a SAS controller since SAS drives are harder to come by. Now Dell doesn't recommend mixing types but I've done it to do some testing. There is no adapter needed :-) I wish there was a SCSI drive to SAS interface like PATA drive to SATA. Unfortunately my PATA adapter is not compliant and won't just work with a SAS cable :-( | On Tue, 10 Oct 2006, Doug Ambrisko wrote: | | > Ceri Davies writes: | > | On Thu, Oct 05, 2006 at 07:29:24AM +0000, John Birrell wrote: | > | > When self-hosting on local disk on the T2000 (with SATA drives) there is a | > | > bug which causes a processor to go off into the weeds. To debug this, kmacy | > | > needs someone to donate another SATA drive. Sun hasn't been responsive to | > | > his request for one. 8-( Can anyone help with that? | > | | > | I didn't think that Sun provided SATA drives for the T2000, only SAS. | > | Do you care about the distinction, or will any 2.5" SATA HDD do? | > | > FWIW, it's been my experience that pretty much any SATA drive will work | > with a SAS controller but not the converse. I've heard they should | > be SATA II but I'm not sure about that. All of the drives I've tried | > have worked but I haven't gone through our complete set. Since SATA | > are easier and cheaper to get I'd go with them. | > | > Doug A.