From owner-freebsd-fs@freebsd.org Wed Sep 23 22:37:23 2015 Return-Path: Delivered-To: freebsd-fs@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 94CE2A07362 for ; Wed, 23 Sep 2015 22:37:23 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32E2F1FC8 for ; Wed, 23 Sep 2015 22:37:22 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wicfx3 with SMTP id fx3so89469699wic.0 for ; Wed, 23 Sep 2015 15:37:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=HbuFCmvkfNXMKuRC0/sN4+S2oWVBF9iPFsSEy4HI/QM=; b=j+/BIlh391h48+cq9VW5mskMs3F4QFMhB1GNL+sAVV+sMW55+16eCtJTqZI+D2p1Uj p+FrDWAce/mu5TjMI3GCY/wjBqsPVn5GYttos5EPVRuf0uervG2reRKINod3cS/0pbFt cNVo7B/vgWh9ndddbC+QtgEVAuMoobBHczsZ+4HOI39I5aLeXDMRDPsev0Y2fEi4XxgG 3XzJckzl9DjGAcDnOVRQmEUD2Od/kCByfdKRnFymzmzZ8JJcYALGsWzgfb39dUKSZWv+ 857gi46AUM2iYimRTaM9MupN6g5TJkK2VhBe+d7RbQ3BR57mwslX0c/NRP/Qtd3Nrk38 wcfQ== X-Gm-Message-State: ALoCoQkleLKpxBmahGFB9zHuD0GS71OjWwo9FLcPRZVlXinGmS/SEfpz+gwtxeCGIiF5sx69LiGM X-Received: by 10.194.93.198 with SMTP id cw6mr43418835wjb.113.1443047835336; Wed, 23 Sep 2015 15:37:15 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id qc4sm9365944wjc.33.2015.09.23.15.37.14 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Sep 2015 15:37:14 -0700 (PDT) Subject: Re: Switching from MFI to MRSAS To: freebsd-fs@freebsd.org References: <56023C15.7080007@fuckner.net> <5602D9E8.2090903@fuckner.net> From: Steven Hartland Message-ID: <56032993.50907@multiplay.co.uk> Date: Wed, 23 Sep 2015 23:37:07 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 22:37:23 -0000 On 23/09/2015 22:32, Ryan Stone wrote: > On Wed, Sep 23, 2015 at 12:59 PM, Tim Gustafson wrote: > >> The mrsas driver man page says that it reports the disks as "da0", >> "da1" and so on, and the man pages about TRIM support all say that it >> works with "ada" and "da" drives. So, I was hoping that the change in >> driver technology would enable the TRIM command to work. >> >> I suppose I could update device.hints and loader.conf as describe, >> reboot, and if the system doesn't come back up, just boot off a thumb >> drive and re-edit those files back to their defaults... >> > The mrsas driver is interesting. Your RAID volumes show up as da0, da1, > etc, but they really shouldn't. I'm doubtful that TRIM will work here > because the drives are not truly directly attached, even though the mrsas > driver is misleading the kernel into thinking that they are. > > You can always give a try, though. camcontrol identify da0 will give you an indication ZFS will tell you straight away after a file delete: sysctl kstat.zfs.misc.zio_trim Regards Steve