BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20181221T160728Z
LOCATION:D163
DTSTART;TZID=America/Chicago:20181112T142500
DTEND;TZID=America/Chicago:20181112T145000
UID:submissions.supercomputing.org_SC18_sess142_ws_pdsw116@linklings.com
SUMMARY:Understanding SSD Reliability in Large-Scale Cloud Systems
DESCRIPTION:Workshop\nI/O, Storage, Workshop Reg Pass\n\nUnderstanding SSD
  Reliability in Large-Scale Cloud Systems\n\nXu, Zheng, Qin, Xu, Wu\n\nMod
 ern datacenters increasingly use flash-based solid state drives (SSDs) for
  high performance and low energy cost. However, SSDs introduce more comple
 x failure modes compared to traditional hard disks. While great efforts ha
 ve been made to understand the reliability of SSDs itself, it remains uncl
 ear how the device-level errors may affect upper layers, or how the servic
 es running on top of the storage stack may affect the SSDs.\n\nIn this pap
 er, we take a holistic view to examine the reliability of SSD-based storag
 e systems in Alibaba's datacenters, which covers about half-million SSDs u
 nder representative cloud services over three years. By vertically analyzi
 ng the error events across three layers (i.e., SSDs, OS, and the distribut
 ed file system), we discover a number of interesting correlations. For exa
 mple, SSDs with UltraDMA CRC errors, while seems benign at the device leve
 l, are nearly 3 times more likely to lead to OS-level error events. As ano
 ther example, different cloud services may lead to different usage pattern
 s of SSDs, some of which are detrimental from the devices perspective.
URL:https://sc18.supercomputing.org/presentation/?id=ws_pdsw116&sess=sess1
 42
END:VEVENT
END:VCALENDAR