From owner-freebsd-questions@FreeBSD.ORG  Thu Aug 28 21:55:06 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@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 33AA710F
 for <freebsd-questions@freebsd.org>; Thu, 28 Aug 2014 21:55:06 +0000 (UTC)
Received: from avasout08.plus.net (avasout08.plus.net [212.159.14.20])
 by mx1.freebsd.org (Postfix) with ESMTP id BEE03179A
 for <freebsd-questions@freebsd.org>; Thu, 28 Aug 2014 21:55:05 +0000 (UTC)
Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout08 with smtp
 id kMuw1o004516WCc01Muxo3; Thu, 28 Aug 2014 22:54:57 +0100
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.1 cv=fsVSZTIf c=1 sm=1 tr=0
 a=lfSX4pPLp9EkufIcToJk/A==:117 a=lfSX4pPLp9EkufIcToJk/A==:17 a=D7rCoLxHAAAA:8
 a=0Bzu9jTXAAAA:8 a=OOzCJWdBeL0A:10 a=RiHyRPlnd20A:10 a=k9qFq3uyW7MA:10
 a=ZTb9aqGL9YkA:10 a=8nJEP1OIZ-IA:10 a=de2h9SMpztOP7ECM7gQA:9 a=wPNLvfGTeEIA:10
Received: from curlew.lan ([192.168.1.13])
 by curlew.milibyte.co.uk with esmtp (Exim 4.83)
 (envelope-from <jmc-freebsd2@milibyte.co.uk>) id 1XN7ei-0001Xq-9p
 for freebsd-questions@freebsd.org; Thu, 28 Aug 2014 22:54:56 +0100
From: Mike Clarke <jmc-freebsd2@milibyte.co.uk>
To: freebsd-questions@freebsd.org
Date: Thu, 28 Aug 2014 22:54:55 +0100
Message-ID: <3415139.ffIAe6AYm2@curlew.lan>
User-Agent: KMail/4.12.5 (FreeBSD/9.3-RELEASE; KDE/4.12.5; amd64; ; )
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 192.168.1.13
X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on curlew.lan
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00
 autolearn=ham autolearn_force=no version=3.4.0
Subject: TRIM considerations when repartitioning a SSD
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="iso-8859-1"
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 21:55:06 -0000


FreeBSD 9.3-RELEASE

I may soon need to repartition a SSD which has a zpool on it and was 
wondering what is the best method of ensuring that all blocks get 
marked as no longer in use.

Is gpart sufficiently TRIM aware to be able to just use gpart delete?

If not then I expect I'll need some or all of the following steps in 
order:

     rm -rf <filesystem>
     zfs destroy -r <zfs_filesystem>
     zpool destroy <pool>
     gpart delete -i <index> <geom>

How far down that list would be the best point to start?

-- 
Mike Clarke