From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 10 21:52:43 2014 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F363BF5B for ; Mon, 10 Mar 2014 21:52:43 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B64D9658 for ; Mon, 10 Mar 2014 21:52:43 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id F1AC2153AA7 for ; Mon, 10 Mar 2014 22:52:41 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63nXCcUt9jFO; Mon, 10 Mar 2014 22:52:16 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id C11B7153AA6 for ; Mon, 10 Mar 2014 22:52:16 +0100 (CET) Message-ID: <531E3410.5090602@digiware.nl> Date: Mon, 10 Mar 2014 22:52:16 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: hardware@freebsd.org Subject: Differences between disk controllers Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2014 21:52:44 -0000 Hi, Running: FreeBSD 10.0-STABLE #0 r262730 I've build a ZFS system, with 4 disks on a regular Marvell controller, and 4 disks on an Areca controller. Disk are 4T WD REDs. I noticed that there were some discrepancies when I build a raidz of 4 "marvell" disks when compared to a raidz on the Areca controller. The essential difference is that on the basic controller the disks are recognised as being 4K disks with quirks. On the Areca controller there is no quirk that matches... Is this a typical problem on the Areca controller? Or does this not work? Thanx, --WjW Basic: mvs0: port 0xb800-0xb8ff mem 0xfcd00000-0xfcdfffff irq 16 at device 0.0 on pci4 mvs0: Gen-IIe, 4 3Gbps ports, Port Multiplier supported with FBS ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 53 With disk: ada0 at mvsch0 bus 0 scbus1 target 0 lun 0 ada0: ATA-9 SATA 3.x device ada0: Serial Number WD-WCC4E0918074 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 3815447MB (7814037168 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> And: arcmsr0: mem 0xfcbff000-0xfcbfffff,0xfb800000-0xfbbfffff irq 18 at device 14.0 on pci3 Areca RAID adapter0: ARC-1220 F/W version V1.49 2010-12-02 With disk: da0 at arcmsr0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: Serial Number WD-WCC4E0959610 da0: 250.000MB/s transfers (125.000MHz, offset 32, 16bit) da0: Command Queueing enabled da0: 3815447MB (7814037168 512 byte sectors: 255H 63S/T 486401C) da0: Delete methods: