From owner-freebsd-hardware@freebsd.org Wed Aug 9 21:37:15 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D96AEDD6778 for ; Wed, 9 Aug 2017 21:37:15 +0000 (UTC) (envelope-from lnb@freebsdsystems.com) Received: from smtpd.barontel.net (smtpd.barontel.net [104.193.49.23]) by mx1.freebsd.org (Postfix) with SMTP id A1E5C264C for ; Wed, 9 Aug 2017 21:37:15 +0000 (UTC) (envelope-from lnb@freebsdsystems.com) Received: (qmail 96204 invoked by uid 89); 9 Aug 2017 21:30:33 -0000 Received: from unknown (HELO smtpd.barontel.net) (172.16.15.9) by vpopmail with SMTP; 9 Aug 2017 21:30:33 -0000 Authentication-Results: smtpd.barontel.net; iprev=pass; auth=pass (plain); spf=pass smtp.mailfrom=freebsdsystems.com Received-SPF: Pass (smtpd.barontel.net: domain of freebsdsystems.com designates 99.237.72.210 as permitted sender) receiver=smtpd.barontel.net; identity=mailfrom; client-ip=99.237.72.210; helo=[192.168.25.24]; envelope-from= Received: from [192.168.25.24] (CPE4c5e0c417c51-CMbc4dfbbdc320.cpe.net.cable.rogers.com [99.237.72.210]) by smtpd.barontel.net (Haraka/2.8.13) with ESMTPSA id 6FE6F683-43FE-4B66-A8A0-75A73CC244CA.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 verify=FAIL); Wed, 09 Aug 2017 17:30:32 -0400 Subject: Re: Do I need SAS drives?.. To: freebsd-hardware@freebsd.org References: <4DFBCE11-913A-4FC9-937D-463B4D49816C@aldan.algebra.com> <362B0950-A244-4C65-89C7-898EFC6A4A1F@fjl.co.uk> <1502292592.2001426.1068163912.1191A246@webmail.messagingengine.com> From: Lanny Baron Organization: Freedom Technologies Corp. FreeBSD Systems Message-ID: <4cd42cce-8e6c-b421-9bf2-08a72945779d@freebsdsystems.com> Date: Wed, 9 Aug 2017 17:30:31 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1502292592.2001426.1068163912.1191A246@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Haraka-FCrDNS: cpe4c5e0c417c51-cmbc4dfbbdc320.cpe.net.cable.rogers.com X-Haraka-Karma: score: 14, good: 327, bad: 7, connections: 336, history: 320, awards: 130, 133, 162, 182, pass:relaying, fail:rcpt_to X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 21:37:15 -0000 Not sure what kind of server you are referring to but our servers can take SAS and SATA at the same time. We build plenty of servers running FreeBSD which in some cases have SATA SSD for boot drives (in a RAID-1) and then X amount of either SATA or SAS or both in a different RAID configuration all connected to the same high quality RAID Controller. I have yet to see any complaint with the configurations we've done for our clients. SAS drives can be much faster. 15K RPM vs. SATA 7.2K. Your choices would depend on how busy the server is. Regards, Lanny On 8/9/2017 11:29 AM, Josh Paetzel wrote: > > > On Wed, Aug 9, 2017, at 09:55 AM, Frank Leonhardt (m) wrote: >> Simple answer is to use either. You're running FreeBSD with ZFS, right? >> BSD will hot plug anything. I suspect 'hot plug' relates to Microsoft >> workaround hardware RAID. >> >> Hot plug enclosures will also let the host know a drive has been pulled. >> Otherwise ZFS won't know whether it was pulled or is unresponsive due to >> it being on fire or something. With 8 drives in your array you can >> probably figure this out yourself. >> >> SAS drives use SCSI commands, which are supposedly better than SATA >> commands. Electrically they are the same. SAS drives are more expensive >> and tend to be higher spec mechanically, but not always so. Incidentally, >> nearline SAS is a cheaper SATA drive that understands SAS protocol and >> has dual ports. Marketing. >> >> Basically, if you really want speed at all costs go for SAS. If you want >> best capacity for your money, go SATA. If in doubt, go for SATA. If you >> don't know you need SAS for some reason, you probably don't. >> >> Regards, Frank. >> >> >> On 9 August 2017 15:27:37 BST, "Mikhail T." >> wrote: >>> My server has 8 "hot-plug" slots, that can accept both SATA and SAS >>> drives. SATA ones tend to be cheaper for the same features (like >>> cache-sizes), what am I getting for the extra money spent on SAS? >>> >>> Asking specifically about the protocol differences... It would seem, >>> for example, SATA can not be as easily hot-plugged, but with >>> camcontrol(8) that should not be a problem, right? What else? Thank >>> you! >>> -- > > I have a different take on this. For starters SAS and SATA aren't > electrically compatible. There's a reason SAS drives are keyed so you > can't plug them in to a SATA controller. It keeps the magic smoke > inside the drive. SAS controllers can tunnel SATA (They confusingly > call this STP (Not Spanning Tree Protocol, but SATA Tunneling Protocol) > It's imperfect but good enough for 8 drives. You really do not want to > put 60 SATA drives in a SAS JBOD) > > SAS can be a shared fabric, which means a group of drives are like a > room full of people having a conversation. If someone starts screaming > and spurting blood it can disrupt the conversations of everyone in the > room. Modern RAID controllers are pretty good at disconnecting drives > that are not working properly but not completely dead. Modern HBAs not > so much. If your controller is an HBA trying to keep a SAS fabric > stable with SATA drives can be more problematic than if you use SAS > drives...and as Frank pointed out nearline SAS drives are essentially > SATA drives with a SAS interface (and are typically under a $20 premium) > > If performance was an issue we'd be talking about SSDs. While SAS > drives do have a performance advantage over SATA in > multiuser/multiapplication environments (they have a superior queuing > implementation) it's not worth considering when the real solution is > SSDs. > > My recommendation is if you have SAS expanders and an HBA use SAS > drives. If you have direct wired SAS or a RAID controller you can use > either SAS or SATA. If your application demands performance or > concurrency get a couple SSDs. They'll smoke anything any spinning > drive can do. >