On 2017-05-16 08:21, Tomasz Torcz wrote:
On Tue, May 16, 2017 at 03:58:41AM +0200, Kai Krakow wrote:
Am Mon, 15 May 2017 22:05:05 +0200
schrieb Tomasz Torcz <to...@pipebreaker.pl>:
My
drive has # smartctl -a /dev/sda | grep LBA 241
Total_LBAs_Written 0x0032 099 099 000 Old_age
Always - 136025596053
Doesn't say this "99%" remaining? The threshold is far from being
reached...
I'm curious, what is Wear_Leveling_Count reporting?
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
9 Power_On_Hours 0x0032 096 096 000 Old_age Always
- 18227
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always
- 29
177 Wear_Leveling_Count 0x0013 001 001 000 Pre-fail Always
- 4916
Is this 001 mean 1%? If so, SMART contradicts datasheets. And I
don't think I shoud see read errors for 1% wear.
The 'normalized' values shown in the VALUE, WORST, and THRESH columns
usually count down to zero (with the notable exception of the thermal
attributes, which usually match the raw value), they exist as a way of
comparing things without having to know what vendor or model the device
is, as the raw values are (again with limited exceptions) technically
vendor specific (the various *_Error_Rate counters on traditional HDD's
are good examples of this). VALUE is your current value, WORST is a
peak-detector type thing that monitors the worst it's been, and THRESH
is the point at which the device manufacturer considers that aspect
failed (which will usually result in the 'Overall Health Assessment'
failing as well), though I'm pretty sure that if THRESH is 000, that
means that the firmware doesn't base it's asse3ssment for that attribute
on the normalized value at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
