From owner-freebsd-ports@freebsd.org Sat Mar 4 13:11:25 2017 Return-Path: Delivered-To: freebsd-ports@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 297ADCF98A5 for ; Sat, 4 Mar 2017 13:11:25 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (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 0B6361346 for ; Sat, 4 Mar 2017 13:11:24 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3vb5lp5JKlzZN; Sat, 4 Mar 2017 07:01:26 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3vb5lp0Szqz48d; Sat, 4 Mar 2017 07:01:26 -0600 (CST) Date: Sat, 4 Mar 2017 07:01:25 -0600 From: "Matthew D. Fuller" To: Kurt Jaeger Cc: Matthias Apitz , freebsd-ports@freebsd.org Subject: Re: running poudriere with 8 builders Message-ID: <20170304130125.GE64417@over-yonder.net> References: <20170304110857.GA2793@c720-r292778-amd64> <20170304115740.GG13006@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170304115740.GG13006@home.opsec.eu> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2017 13:11:25 -0000 On Sat, Mar 04, 2017 at 12:57:40PM +0100 I heard the voice of Kurt Jaeger, and lo! it spake thus: > > /pou is on an Samsung SSD 840 EVO 250GB: > > smartctl says: > > 9 Power_On_Hours 0x0032 091 091 Always - 41885 > 12 Power_Cycle_Count 0x0032 099 099 Always - 8 > 177 Wear_Leveling_Count 0x0013 083 083 Always - 199 > > The Wear_Leveling_Count shows that it's probably beyond the spec > already 8-} Actually, I'm pretty sure it means the opposite 8-} It's my understanding that the "Raw" value on them is pretty much roughly the actual count of levelled drive writes, and the cooked "Value" (/worst, though that doesn't make a difference on that attribute) winds up basically meaning "percent of rated life left"[0]. So you've got ~200 drive writes, and have used about 17% of its life. On a 250GB 840 Evo I have, in somewhat easier use than being poundriered senseless: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 177 Wear_Leveling_Count PO--C- 095 095 000 - 57 It's in a mirror with a similarly sized MX100, which (with its different attributes; can't be consistent, y'know) says 202 Percent_Lifetime_Used P---CK 095 095 000 - 5 which agrees; I've only got 19/20ths of their lifespan to go before I gotta cough up umpty-dozens of dollars to replace them. [0] For most SMART attributes, the cooked 'value' actually starts at 100 and counts down, with the Threshold level being where it starts claiming to be deeply unhappy. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.