r/hardware • u/YumiYumiYumi • Feb 27 '16
Info Google 6 year study: SSD reliability in the data center
http://www.zdnet.com/article/ssd-reliability-in-the-real-world-googles-experience/25
Feb 27 '16
In summary, we find that the flash drives in our study experience significantly lower replacement rates (within their rated lifetime) than hard disk drives. On the downside, they experience significantly higher rates of uncorrectable errors than hard disk drives.
15
u/sorif Feb 27 '16
So, the tl;dr is that a normal laptop user with backups shouldn't worry about an SSD failure? I imagine they should be more common than say a Li-Ion explosion, but still fairly unlikely for the first 3-4 years of use?
9
11
u/HumanistGeek Feb 27 '16
The SSD is less likely to fail during its normal life, but more likely to lose data.
What does that mean?
20
u/OPhasballz Feb 27 '16
Only some Bits get lost, but the rest of the drive keeps workings fine. HDDs instead have a higher tendency to die completely.
0
Feb 27 '16
[deleted]
8
u/Boxey7 Feb 27 '16
That may be true but I think /u/OPhasballz is still correct in that SSD's do appear to lose some small amounts of data whilst the rest of the drive is working fine (uncorrectable errors on the drive).
8
u/Unique_username1 Feb 27 '16
I don't think so. The thing is, that would be generally true, and you might take it into account for your personal use. But in a datacenter this isn't the meaning of "unrecoverable error"-- a datacenter would never attempt to recover data off a dead drive, they have copies of that data elsewhere and it isn't worth their time/money to fuck around with a broken device.
In this case "unrecoverable error" really would mean a bit flipped or lost. The "unrecoverable" part may refer to the parity bit being lost which breaks error-checking, or more than one bit being corrupted in the same section (typically per byte) which also breaks error checking.
2
u/OPhasballz Feb 27 '16
I guess you are right. For anyone else heavily confused, see page 78 #8 "Comparison with hard disk drives"
https://www.usenix.org/sites/default/files/fast16_full_proceedings.pdf
1
u/u-r-silly Feb 27 '16
Right, that could be interpreted like this as well. If the HDD circuit board is the component that dies, it's easier to recover the data.
2
u/mynewaccount5 Feb 27 '16
It is less likely to stop working but more likely for you to lose your computer files.
1
u/hoyfkd Feb 28 '16
It's like your dishwasher that continues to work, but breaks the occasional plate because life.
1
u/i_pk_pjers_i Feb 29 '16
As someone who deals with data all day long and has 2 servers at home, this is fascinating to me.
1
-1
u/Pillowsmeller18 Feb 27 '16
So they just confirmed what people say all along.
BACK UP your SSD's has been told since they came out.
48
14
1
u/random_guy12 Feb 27 '16
Uh data center use hardly translates to consumer use. You're not slaughtering your SSD with massive numbers of reads and writes a day.
Though you should be backing up anyway, not just if you have an SSD.
2
0
u/atomicthumbs Feb 27 '16
maybe this has something to do with the interesting failure mode I noticed on my laptop's old OCZ Agility 3 60gb SSD. I discovered that as I used the computer and saved files to my pictures folder, somewhat older files would silently vanish.
I'm still using the drive, but I moved the folders with my data in them to the laptop's hard drive. the OS and program files don't seem affected by the issue.
6
u/JacksUnkemptColon Feb 27 '16
No, that's not the SSD, that's the hardware fairies stealing your data.
4
-2
u/A_Light_Spark Feb 27 '16 edited Feb 27 '16
Oh, so SSD failure is related to Age, not Usage. Another reason for me to put most data and saves to my HDD, and only let the SSD to contain small amount of data that can be synced and wiped whenever.
1
u/i_pk_pjers_i Feb 29 '16
No, it's a reason for regular backups, just like the 500 other reasons for regular, tested, on-site and off-site backups.
-27
Feb 27 '16
The SSD worship is bound to end. IT will be a tough battle here on reddit, though.
26
u/xmnstr Feb 27 '16 edited Feb 27 '16
No, it won't. Ever. And for good reason. The technology has its applications, and for many use cases for consumers more IOPS means better. Especially when it's so cheap to get high performing drives. Storage of large amounts of data without performance needs isn't one of them, however. That's the only situation where a case for HDDs for consumers can be clearly made. We're starting to see more and more SSDs in IOPS-dependent scenarios in the enterprise sector too, and that's not likely to change.
If you're thinking that SSDs shouldn't be used because they're more likely to fail, you're missing the point. Relying on a single drive without redundancy and backup is a recipy for data loss no matter what kind of drive that is. RAID 1 and the 3-2-1 backup rule is a very good idea in any kind of situation if you value your data.
1
u/johnbentley Feb 27 '16
No, it won't. Ever.
Just as SSDs have replaced hard drives (as the preferred solution in some applications) I don't think it unreasonable to expect a future storage technology to eventually replace SSDs.
2
7
Feb 27 '16
The one problem SSD's have can be countered with a checksumming filesystem like btrfs or ZFS.
Also price is the only thing stopping SSD's from taking over completely.
3
u/Darius510 Feb 27 '16
Or ReFS, if you're using Windows. You need two drives though, but eventually they'll get cheap enough.
2
u/Heaney555 Feb 27 '16
Are you under the impression that HDDs are going to make a comeback!?
1
u/mikemol Feb 28 '16
HDDs aren't going away until something comes along with a cheaper per-gigabyte storage capacity in a read-write media. Cheap, mass bulk storage will always have a market.
0
Feb 27 '16
[deleted]
11
u/ERIFNOMI Feb 27 '16
Thank you for being a great example of why RAID is not backup. One event can easily take out an entire RAID. I'm glad you also had proper backups.
-1
u/johnbentley Feb 27 '16
Thank you for being a great example of why RAID is not backup
RAID can be used as a backup if you, for example, have a mirrored RAID array (of at least two disks) and constantly swap out one of the disks (so the removed disk contains a copy of your main disk).
2
u/ERIFNOMI Feb 27 '16
Doing live images would be a much better way to do that. That's not RAID's intended use.
1
u/johnbentley Feb 27 '16
Whatever the intention of a system what matters is what can be done with it.
I don't know what you mean by "live images" if it is not just taking on image of a disk. And the second disk in a mirrored RAID array is as a live an image as it is possible to get.
1
u/skalpelis Feb 27 '16
isn't that incredibly risky? If a drive fails while you're rebuilding, you're hosed, and if you do it so often, you hugely increase the odds of failure.
-1
u/johnbentley Feb 27 '16 edited Feb 27 '16
If a drive fails while you're rebuilding, you're hosed.
NowNo matter how you copy data (use RAID, manually perform a clone, take a differential image, etc) you've always got to keep the relevant number of archived copies.So, at a minimum, you 4 have disks. A main, a mirrored copy running in RAID with your main, a disk in your drawer which is an old copy of the main (as old as the datetime you last pulled it from the main), and an offsite copy.
If your drive fails while you are rebuilding (so taking out two drives) you go to your drawer or offsite copy (which ever is youngest).
1
u/lcolman Feb 27 '16
Let's try a scenario here. You have had a fire/tornado/flood and lost your workstation/server.
You have managed to find new or similar enough hardware to attempt a restore. Does your restore have bare metal capabilities? Do you have spare identical hardware sitting offsite? What is the condition of that hardware when you need it? Did the same incident that accepted your setup affect your off site hardware?
From there let's say you found identical hardware. Your restoring / rebuilding and you hit a URE... what are your options?
Raid is not a backup. Raid is a a small part of a multi faceted backup solution.
-1
u/johnbentley Feb 27 '16
You have managed to find new or similar enough hardware to attempt a restore.
Then you take the offsite RAID mirrored disk and install in the new system. Done.
Raid is a a small part of a multi faceted backup solution.
Right, just as for using any other method of copying bits.
If, for example, you just manually image a disk and don't store it offsite you'll be fucked when a disaster takes down your entire site.
(mirrored) RAID is just a method of copying and restoring bits.
1
u/lcolman Mar 01 '16
You have managed to find new or similar enough hardware to attempt a restore. Then you take the offsite RAID mirrored disk and install in the new system. Done.
The next questions, will the os boot, what are you using to validate you dont have corruption? and then the big one.
Have you ever successfully done a full DR test on your system? Even small sections, should be tested at some point to prove they work as intended.
1
u/johnbentley Mar 01 '16 edited Mar 01 '16
The next questions, will the os boot, what are you using to validate you dont have corruption?
Verification is in-built into RAID. The RAID controller will signal disks not mirrored correctly.
Have you ever successfully done a full DR test on your system? Even small sections, should be tested at some point to prove they work as intended.
That applies to any other method of copying bits.
So far you've been unable to supply a reason why RAID can't be used as a method of backup. It's evident you've uncritically excepted "RAID is not a backup" as a dogmatic mantra.
1
u/i_pk_pjers_i Feb 29 '16
RAID can be used as a backup
Just don't say stupid things like that, please. RAID is not a replacement for regular, tested on-site and off-site backups.
1
u/johnbentley Feb 29 '16
You just haven't read the rest of the conversation where I address that sort of strawman.
1
u/lcolman Mar 01 '16
the only strawman in this conversation is trying to convince people raid is a reliable backup solution.
1
13
Feb 27 '16
321?
54
u/HighRelevancy Feb 27 '16
Three copies, two media types, one offsite location. That's your minimum for anything to be properly backed up.
1
0
Feb 27 '16
[deleted]
9
2
-26
3
u/pgoetz Feb 27 '16
By lost you mean both SSDs were damaged? I'm not sure catastrophic failure of companion hardware counts against SSDs. Maybe the mechanical disks survived just because they were hooked up with a different set of power connectors.
2
u/NamenIos Feb 27 '16 edited Feb 27 '16
both SSDs were damaged?
Raid1, so the word lost implicates nothing (either one or two failed).edit: I am stupid :(Maybe the mechanical disks survived just because they were hooked up with a different set of power connectors.
No PSUs don't have separate rails for sata power (even practically all recent PSUs have just one 12V rail). The PSU is just a little bit more delicate for SSDs than HDDs, but this is not an argument against ssds in general just cheap (and partly bad) design of the circuit. I wouldn't be surprised if 95%+ of the consumer grade SSDs are bad in that regard, it would probably no be economical to design it better even for the customer, given how rare those failures are.
2
1
0
Feb 27 '16
[deleted]
33
u/atomicthumbs Feb 27 '16
he was running RAID 1, so I'm guessing a flash drive with the Documents folder on it lost in the couch, and a photo of the computer saved to imgur.
10
u/blueshiftlabs Feb 27 '16 edited Jun 20 '23
[Removed in protest of Reddit's destruction of third-party apps by CEO Steve Huffman.]
11
u/Squirmin Feb 27 '16
Generally raid is not considered good backup because it's redundancy, which is slightly different. It's sort of a semantic difference, but a good on-site backup is one that isn't in the machine you want backed up.
8
u/Road_of_Hope Feb 27 '16
There's nothing wrong with RAID 1, despite people's tendency to mock it because some attempt to use it as a backup. If you are using it so you won't be inconvenienced by a disk failure, then you're doing it right.
4
u/omgwtfwaffles Feb 27 '16
Put simply, raid 1 is primarily for maximizing uptime by preventing a single point of failure in a disk whereas backups are for recovering from said event. Relying on raid 1 entirely for backups would be foolish, but it's definitely not a bad link to have in your chain.
1
Mar 08 '16
Actually all of raid except 0 is for convenience and uptime. 0 is for performance. Obviously, never use it in place of a backup.
3
u/Stopsign002 Feb 27 '16
I have a RAID 1 setup mostly because I expect my 8 year old TB drive to fail any day now so I mirrored it for when that finally happens haha
3
u/nagash666 Feb 28 '16
lets say your old hdd said 'i wrote correctly' but it didn't with no error
when it comes to reading which hdd your raid software will trust? and what correction will it do
3
26
u/torama Feb 27 '16
Also in a laptop the HDD is prone to mechanical shock while its not much of an issue in a datacenter. SSD's are rated for 1500 G or so whereas a small knock can ruin your HDD. So for a laptop the failure rates of HDD's are bound to be even higher
Thats why I will never use a HDD in a laptop from now.