From owner-freebsd-questions@FreeBSD.ORG Tue Sep 9 16:08:05 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8658CE4C for ; Tue, 9 Sep 2014 16:08:05 +0000 (UTC) Received: from mail.pchotshots.com (mail.pchotshots.com [12.172.123.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 450EFB5 for ; Tue, 9 Sep 2014 16:08:04 +0000 (UTC) Received: (qmail 35689 invoked by uid 89); 9 Sep 2014 16:10:02 -0000 Received: from unknown (HELO ?12.172.123.228?) (bmettee@pchotshots.com@12.172.123.228) by mail.pchotshots.com with ESMTPA; 9 Sep 2014 16:10:02 -0000 Message-ID: <540F25C0.7070202@pchotshots.com> Date: Tue, 09 Sep 2014 12:07:28 -0400 From: Brad Mettee User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: A litmus check request References: <540E21A0.4070103@comcast.net> <20140909162023.3f0cb6d7@gumby.homeunix.com> In-Reply-To: <20140909162023.3f0cb6d7@gumby.homeunix.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 16:08:05 -0000 On 9/9/2014 11:20 AM, RW wrote: > On Mon, 08 Sep 2014 15:37:36 -0600 > Dave Babb wrote: > >> I am about to do a lot of compiling. My copy of FreeBSD10.0 x64 P7 >> runs on a 1TB Samsung EVO. I used wblock's excellent articles to set >> it all up so that trim was utilized. >> >> I am asking that someone please review this attached fstab and >> validate for me, that at no time will any compilation intermediate >> files, or ".o" files will be written to the SSD. I am trying to >> protect the SSD. > If you haven't already done so I'd suggest you have a look at the > output of smartctl -a (from sysutils/smartmontools) and see > if Samsung have added an attribute to track total writes into the NAND > flash. > > I recently installed an SSD, and found buildworld produced 6 GB > of writes and buildkernel a further 6 GB. It's a substantial > overhead, but not ruinous if you occasionally want to install world by > rebooting into single-user mode. An alternative might be to build with > MAKEOBJDIRPREFIX set to /tmp/obj and then copy /tmp/obj to /usr/obj. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > The Tech Report has been an SSD Endurance Experiment since Aug 2013. Three out of six starting drives have made it to the 1PB mark, the other three all made it up to 600TB. All of the drives are consumer grade, not server grade. Being careful is good, but depending on brand of drive, and several other factors, the 200TB write life looks like be a bit of an underestimate. As long as you try to reasonably minimize your writes to the SSD, it doesn't look like you need to be too paranoid about it. http://techreport.com/review/24841/introducing-the-ssd-endurance-experiment Links to updates on the experiment can be found at the bottom of the last page (before the comments). Hope this helps. -- Brad Mettee