From owner-freebsd-current@freebsd.org Fri Apr 15 11:20:19 2016 Return-Path: Delivered-To: freebsd-current@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 31678AEDF41 for ; Fri, 15 Apr 2016 11:20:19 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 C5CB21195 for ; Fri, 15 Apr 2016 11:20:18 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x234.google.com with SMTP id a140so26718723wma.0 for ; Fri, 15 Apr 2016 04:20:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=fLHpRyMkd6Im8dZcFUGEsGDtTgdb/26dv3r3pz2CTzk=; b=JvEOh3qp1k7ngeOqzT9zkFjKvWqv5HDiLGCAk7lKThkJMldvSkZN2/v5JXUWLdg5EA fhrH1hOWPA5gcjG82gunMZjZWyt6w24/XnfE8xRayDDEooe31SoJKfA0XKBWnzT2s7tx +3Ky3VnOw5wtv3U9EVjmujkOWdf1XKdLSL0dElvjHxRxJpS0mBWnunP5Ea9YBZWiXIvH MY8wg8DyL4iNw45fAov9J72Vj9QUyLaKIN/uaLlHC30AuJVPL/2kuDX39YA/ddBqu0MC 1t2uiNNlZn5fQQa7roUG2sgrnXPSAnU3/+8BOtZB9Wz6Gk+k/YlfODOHO3BZ2X9vLrQA hqCA== 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-transfer-encoding; bh=fLHpRyMkd6Im8dZcFUGEsGDtTgdb/26dv3r3pz2CTzk=; b=ivFHO2SAN46OocZoCOPTkQePa3EAIbJW/3xMB+I+hk8dPTwNNTQE/UXvXYrS9dNUMs VBlHr1+tOjETIMdOAyU97tEnHsgMGgJDA6OOCEQQE05LYw79kv+1Z4M7dM17MVNrfD7e XzaZvbqAYeYWynCpS74yLom8S9K6bTextlIn4j0QyG9ibWm04u+Di/dxtMiz98P61mlT yhJxixrs5MOq1hwKxvQbz3YmQdSnShS5U7j/sFiOFifo0vVBrzqwbMFDFB0cCIyfSqMY aDT7k/I1w9uMMjBnV4LRVnTVs1xA0vMl1lx4/RZIJVkIDOFOsY6gO1hOk05Gx6RRh6qH 27pg== X-Gm-Message-State: AOPr4FXmV/osGIMW+qfLhM8GdJsZs+eOBMcy/c6VieZKeq42G33kjpfrz9Gju0m9OklJKQHA X-Received: by 10.28.189.133 with SMTP id n127mr4015142wmf.5.1460719215880; Fri, 15 Apr 2016 04:20:15 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id d131sm11128411wmd.12.2016.04.15.04.20.14 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2016 04:20:15 -0700 (PDT) Subject: Re: Samsung SSD TRIM [Was: Heads up] To: freebsd-current@freebsd.org References: <57109CB7.3020204@FreeBSD.org> <20160415081130.GH2282@home.opsec.eu> From: Steven Hartland Message-ID: <5710CE6F.6010408@multiplay.co.uk> Date: Fri, 15 Apr 2016 12:20:15 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160415081130.GH2282@home.opsec.eu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2016 11:20:19 -0000 On 15/04/2016 09:11, Kurt Jaeger wrote: > Hi! > > avg wrote: >> For what it's worth, I have been using the following SSDs since September of 2015 : >> >> ada2: ACS-2 ATA SATA 3.x device >> ada3: ACS-2 ATA SATA 3.x device > I have one in use with zfs and trim: > > ada1: ACS-2 ATA SATA 3.x device > > Works as my ports build hosts, and is fine as far as I can see. > Prior to Warners commit there was no NCQ TRIM support in FreeBSD, so while it was working with standard non-NCQ TRIM (and I can corroborate that as we use the 840's and 850's all over with ZFS with TRIM enabled) its possible that it could cause issues when NCQ TRIM comes into play. From what I read when this issue first came to light, I believe the actual issue was a Linux kernel bug not a FW bug in Samsung drives that caused the corruption. This is the thread which details said issue: http://www.spinics.net/lists/raid/msg49440.html Regards Steve