From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 18 21:58:58 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 34E9756B for ; Fri, 18 Jan 2013 21:58:58 +0000 (UTC) (envelope-from fodillemlinkarim@gmail.com) Received: from mail-ia0-x22c.google.com (ia-in-x022c.1e100.net [IPv6:2607:f8b0:4001:c02::22c]) by mx1.freebsd.org (Postfix) with ESMTP id E80A1A06 for ; Fri, 18 Jan 2013 21:58:57 +0000 (UTC) Received: by mail-ia0-f172.google.com with SMTP id u8so1883054iag.31 for ; Fri, 18 Jan 2013 13:58:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XdrpOqpTCsstLxtI0mAw7/1is9pU0w7nesKd4m0utZ0=; b=Qk70mwgUGYjhzo1Nudp+FuV5KlGWBy1usM1O6mK/CLdGFjwEpg/H/zeYm8M234UiY+ KQpqN9jSzMESh5TGeZkNA/Zq9ZI3/ue7CLc4H795aVPCIpQJqhNCrl91/3s9QvXVmGh1 JbF3Y/uQ33vocsNd+5/7nid7OTNpP1Ow3tB9yh9Itdkm3/H6kVuaOQD/998vn1sKzxX2 mAegult4jjO/hU486cVNSLhPAn3ZRD1cJN1bTOBskdLKUwfSImU+Ag1cjwcqrV+khvby SkCb7UrEiFGY2IUFzKlYrpc4IRCTLM/O2HD94nWooqQP7gIL/IiRlkrvxnC3OpDNIZif IzyA== X-Received: by 10.50.163.104 with SMTP id yh8mr3302744igb.112.1358546337662; Fri, 18 Jan 2013 13:58:57 -0800 (PST) Received: from [10.0.0.131] ([24.225.136.71]) by mx.google.com with ESMTPS id df6sm2237395igb.15.2013.01.18.13.58.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Jan 2013 13:58:56 -0800 (PST) Message-ID: <50F9C597.7010608@gmail.com> Date: Fri, 18 Jan 2013 16:58:47 -0500 From: Karim Fodil-Lemelin User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Mark Felder Subject: Re: IBM blade server abysmal disk write performances References: <50F87741.4030201@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 18 Jan 2013 22:19:42 +0000 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 21:58:58 -0000 On 18/01/2013 10:16 AM, Mark Felder wrote: > On Thu, 17 Jan 2013 16:12:17 -0600, Karim Fodil-Lemelin > wrote: > >> "SAS controllers may connect to SATA devices, either directly >> connected using native SATA protocol or through SAS expanders using >> SATA Tunneled Protocol (STP)." >> The systems is currently put in place using SATA instead of SAS >> although its using the same interface and backplane connectors and >> the drives (SATA) show as da0 in BSD _but_ with the SATA drive we get >> *much* better performances. I am thinking that something fancy in >> that SAS drive is not being handled correctly by the FreeBSD driver. >> I am planning to revisit the SAS drive issue at a later point >> (sometimes next week). > > Your SATA drives are connected directly not with an interposer such as > the LSISS9252, correct? If so, this might be the cause of your > problems. Mixing SAS and SATA drives is known to cause serious > performance issues for almost every > JBOD/controller/expander/what-have-you. Change your configuration so > there is only one protocol being spoken on the bus (SAS) by putting > your SATA drives behind interposers which translate SAS to SATA just > before the disk. This will solve many problems. Not sure what you mean by this but isn't the mpt detecting an interposer in this line: mpt0: port 0x1000-0x10ff mem 0x99910000-0x99913fff,0x99900000-0x9990ffff irq 28 at device 0.0 on pci11 mpt0: MPI Version=1.5.20.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (14 Max) Also please not SATA speed in that same hardware setup works just fine. In any case I will have a look. Thanks, Karim.