Reliability » History » Version 3

Steve Welburn, 2014-09-15 10:57 AM

1 1 Steve Welburn
h2. Reliability
2 1 Steve Welburn
3 1 Steve Welburn
h3. Laptop Reliability
4 1 Steve Welburn
5 1 Steve Welburn
* 2011 PC World Laptop Reliability Survey from 63,000 readers:
6 1 Steve Welburn
** 22.6% had signifcant problems during the product's lifetime
7 1 Steve Welburn
** Of which...
8 1 Steve Welburn
*** 19% had OS problems ~1 in 25 of all laptops
9 1 Steve Welburn
*** 18% had HDD problems ~1 in 25 of all laptops
10 1 Steve Welburn
*** 10% PSU problems ~1 in 50 of all laptops
11 1 Steve Welburn
12 1 Steve Welburn
PC World 2011 - http://tinyurl.com/876qza5
13 1 Steve Welburn
14 1 Steve Welburn
h3. Hard Disk Failures
15 1 Steve Welburn
16 1 Steve Welburn
* Failure Trends In A Large Disk Drive Population
17 1 Steve Welburn
** Usenix conference on File and Storage Technologies 2007 (FAST '07)
18 1 Steve Welburn
** Eduardo Pinheiro & Wolf-Dietrich Weber, Google Inc.
19 1 Steve Welburn
* Data collected from over 100,000 disk drives at Google
20 1 Steve Welburn
* As part of repairs procedures:
21 1 Steve Welburn
** ~13% of disk drives replaced over 3 years
22 1 Steve Welburn
** ~20% of disk drives replaced over 4 years
23 1 Steve Welburn
24 1 Steve Welburn
Article: http://tinyurl.com/octz6b
25 1 Steve Welburn
26 1 Steve Welburn
[[Failure Trends In A Large Disk Drive Population|More info]]
27 2 Steve Welburn
28 2 Steve Welburn
h3. Cloud Failures
29 3 Steve Welburn
30 1 Steve Welburn
* Hazards of the Cloud: Data-Storage Service’s Crash Sets Back Researchers "Chronicle Of Higher Education, 12 May 2014":http://chronicle.com/blogs/wiredcampus/hazards-of-the-cloud-data-storage-services-crash-sets-back-researchers/52571
31 3 Steve Welburn
** "Dedoose":http://www.dedoose.com systems failed 
32 3 Steve Welburn
** Dedoose blog post 9 May 2014 : "Dedoose's Black Eye":http://blog.dedoose.com/2014/05/dedooses-black-eye-crash-and-recovery-efforts/
33 1 Steve Welburn
34 2 Steve Welburn
bq. In short, work done on one aspect of Dedoose led to the failure of another, cascading to pull down all of Dedoose.  The timing was particularly bad because it occurred in the midst of a full database encryption and backup.  This backup process, in turn, corrupted our entire storage system. 
35 2 Steve Welburn
36 3 Steve Welburn
** Crash Updates: 11 May 2014 "Crash Updates":http://blog.dedoose.com/2014/05/dedoose-crash-updates/
37 2 Steve Welburn
38 2 Steve Welburn
bq. The backup file of data through April 11th has been pieced back together, however it remains encrypted and corrupted.  We are running a variety of tools on the file to restore things to a state where we can merge the data back into the live database. 
39 1 Steve Welburn
40 3 Steve Welburn
** Recovery Efforts: 14 May 2014 "Data Recovery":http://blog.dedoose.com/2014/05/dedoose-update-significant-data-recovery-successful-how-to-save-a-project-locally/
41 2 Steve Welburn
42 2 Steve Welburn
bq. At this point, we are very happy to report that we have recovered data entered to Dedoose through March 30th.  We are still working on the details of how these data will be safely merged into the master database.
43 2 Steve Welburn
44 3 Steve Welburn
** Merging Recovered Data: 16 May 2014 "Data Merging":http://blog.dedoose.com/2014/05/dedoose-update-recovered-data-to-be-merged-tonight-and-some-reminders/
45 2 Steve Welburn
46 2 Steve Welburn
bq. The data that have been viewable on our staging environment (stage.dedoose.com/app) represent those that have been recovered for work added to Dedoose between March 2nd and March 30th.  These data will be merged back into the live database beginning tonight at 8pm PST.  It is necessary to shut down Dedoose services during this procedure which should last approximately 4 hours.