From owner-freebsd-stable@FreeBSD.ORG Wed Jun 5 22:13:37 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 11999ECB for ; Wed, 5 Jun 2013 22:13:37 +0000 (UTC) (envelope-from prvs=1868436c14=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id AADC41727 for ; Wed, 5 Jun 2013 22:13:36 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50004176069.msg for ; Wed, 05 Jun 2013 23:13:35 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 05 Jun 2013 23:13:35 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1868436c14=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@FreeBSD.org Message-ID: <22BEEC35F8964CACB8E625DA3068A12F@multiplay.co.uk> From: "Steven Hartland" To: "Dmitry Morozovsky" , References: Subject: Re: TRIM support through ciss Date: Wed, 5 Jun 2013 23:13:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2013 22:13:37 -0000 ----- Original Message ----- From: "Dmitry Morozovsky" To: Sent: Wednesday, June 05, 2013 11:00 PM Subject: TRIM support through ciss > Dear colleagues, > > I have a DB server with ciss and a bunch of disks (8 SAS + 2 Intel SATA SSD). > > However, this setup does not seem to support TRIM on SSDs: > > kstat.zfs.misc.zio_trim.bytes: 0 > kstat.zfs.misc.zio_trim.success: 0 > kstat.zfs.misc.zio_trim.unsupported: 418 > kstat.zfs.misc.zio_trim.failed: 0 > > > Excerpt from dmesg about SSD: > > da9 at ciss0 bus 0 scbus0 target 9 lun 0 > da9: Fixed Direct Access SCSI-5 device > da9: Serial Number PACCR9SZ7KJS > da9: 135.168MB/s transfers > da9: Command Queueing enabled > da9: 114439MB (234371520 512 byte sectors: 255H 32S/T 28722C) > da9: quirks=0x1 > da9: Delete methods: > > the last line bothers me... > > Is there any tuning I missed? What your seeing there is that the RAID array doesn't support any DELETE methods. For ZFS you really don't want to use a HW RAID, its much better to just give ZFS the raw disks as you gain nice features like self healing :) I've never used ciss, but if you can configure the disks as JBOD it may mean it can then support a delete method. In addition for TRIM to work all data disks in a pool need to support a delete method. L2ARC disks are treated seperately. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.