pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Yeb Havinga <yebhavinga@gmail.com>
To: Florian Weimer <fweimer@bfk.de>
Cc: Andy <angelflow@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: BBU still needed with SSD?
Date: Tue, 19 Jul 2011 14:16:07 +0200
Message-ID: <4E257587.3040704@gmail.com> (raw)
In-Reply-To: <82livubix4.fsf@mid.bfk.de>
References: <1310953399.25726.YahooMailClassic@web111304.mail.gq1.yahoo.com>
	<4E23E72B.2070508@gmail.com>
	<82vcuyd7p5.fsf@mid.bfk.de>
	<4E255DF9.20005@gmail.com>
	<82y5zubl90.fsf@mid.bfk.de>
	<4E2569B0.2050307@gmail.com>
	<82livubix4.fsf@mid.bfk.de>

On 2011-07-19 13:37, Florian Weimer wrote:
> Is this "Total_LBAs_Written"?
I got the same name "Total_LBAs_Written" on an 5.39 smartmontools, which 
was renamed to 241 Lifetime_Writes_GiB after upgrade to 5.42. Note that 
this is smartmontools new interpretation of the values, which happen to 
match with the OCZ tools interpretation (241: SSD Lifetime writes from 
host          Number of bytes written to SSD: 448 G). So for the Intels 
it's probably also lifetime writes in GB but you'd have to check with an 
Intel smart values reader to be absolutely sure.
>    The values appear to be far too low:
>
> 241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       188276
> 242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       116800
>
> 241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       189677
> 242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       92509
Hmm that would mean 188TB written. Does that value seem right to your 
use case? If you'd write 100MB/s sustained, it would take 22 days to 
reach 188TB.
> The second set of numbers are from the drive which wears more quickly.
It's strange that there's such a large difference in lifetime left, when 
lifetime writes are so similar. Maybe there are more small md metadata 
updates on the second disk, but without digging into md's internals it's 
impossible to say anything constructive about it.

Off-topic: new cool tool in smartmontools-5.4x: 
/usr/sbin/update-smart-drivedb :-)

-- 

Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data




view thread (17+ messages)  latest in thread

Message-ID: <4E257587.3040704@gmail.com>
Permalink:  ../4E257587.3040704@gmail.com/
Also on:    postgresql.org/message-id/4E257587.3040704@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: yebhavinga@gmail.com, fweimer@bfk.de, angelflow@yahoo.com
  Subject: Re: BBU still needed with SSD?
  In-Reply-To: <4E257587.3040704@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox