Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Sep 2014 22:25:43 +0100
From:      RW <rwmaillists@googlemail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: TRIM considerations when repartitioning a SSD
Message-ID:  <20140908222543.78ce723a@gumby.homeunix.com>
In-Reply-To: <3289227.doeQfn2zmQ@curlew.lan>
References:  <3415139.ffIAe6AYm2@curlew.lan> <CA%2BtpaK0UpDCvBuMpnOkDXNfcnkuBfB-6tv2cMuyRjah5Z3xPRQ@mail.gmail.com> <3289227.doeQfn2zmQ@curlew.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 08 Sep 2014 15:08:26 +0100
Mike Clarke wrote:

> On Thursday 28 Aug 2014 17:24:04 Adam Vande More wrote:
> > On Thu, Aug 28, 2014 at 4:54 PM, Mike Clarke
> > <jmc-freebsd2@milibyte.co.uk>
> > wrote:
> > > 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?
> > Extremely doubtful that it is.  You generally must reset the drive
> > eg
> > 
> > camcontrol security da4 -s buhbyesweetdata -e buhbyesweetdata
> 
> I've tried this but it failed

newfs -tE will trim the free space on the UFS filesystem it creates.
Even if you don't want UFS, you could run it on the raw drive, the
difference is most likely negligible.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140908222543.78ce723a>