A deep dive of the methodology and tooling that we use at Meta, to improve debuggability of failures in the datacenters, especially for failures on components like SSDs where privacy requirements might prohibit us from sending the components back for FA or add custom instrumentations in our datacenter. In particular, we will talk about how the tool tracewatch coupled with Latency Monitoring log page helps us trigger trace collection on failures using BPF based triggers.

SMB3 has seen significant adoption as the storage protocol of choice for running private cloud deployments. In this iteration of the talk, we’ll update the audience on SMB protocol changes as well as improvements to the Windows implementation of the SMB server and client. Added to the SMB protocol is a new server-to-client notification mechanism, which enables a variety of novel use cases. We’ll present the details of protocol messaging (new message types, etc) as well as the one scenario which leverages this new mechanism (server-triggered graceful session closure).

DNA data storage will dramatically effect the way organizations think about data retention, data protection, and archival by providing capacity density and longevity several orders of magnitude beyond anything available today, while reducing requirements for both power, cooling, and fixity checks. One of challenges of any long term archival storage is being able to recover the data after possibly decades or longer. To do this, the reader must be able to bootstrap the archive, akin to how an OS is loaded after the master boot record is loaded.

DMTF’s Redfish® is a standard API designed to deliver simple and secure management for converged, hybrid IT and the Software Defined Data Center (SDDC). This presentation will provide an overview of DMTF’s Redfish standard. It will also provide an overview HPE’s implementation of Redfish, focusing on their storage implementation and needs. HPE will provide insights into the benefits and challenges of the Redfish Storage model, including areas where functionality added to SNIA™ Swordfish is of interest for future releases.

The Key Per IO (KPIO) project is a joint initiative between NVM Express® and the Trusted Computing Group (TCG) Storage Work Group to define a new KPIO Security Subsystem Class (SSC) under TCG Opal SSC for NVMe® class of Storage Devices. Self-Encrypting Drives (SED) perform continuous encryption on user accessible data based on contiguous LBA ranges per namespace. This is done at interface speeds using a small number of keys generated/held in persistent media by the storage device. KPIO will allow large number of encryption keys to be managed and securely downloaded into the NVM subsystem.

One fallout of Samba's protection against symlink races was a slowdown of pathname handling. This talk will present the current status at the time of the conference of the ongoing work to fix the slowdown by using modern Posix and in particular Linux/FreeBSD APIs.

NOTE: this paper was developed by Ziye Yang, a Staff Software Engineer at Intel and is being presented by colleague Yadong Li, a Principal Engineer in the Ethernet Products Group at Intel. In many usage cases, FaaS applications usually run or deployed in container/Virtual machine environment for isolation purpose.

Data bytes stored continues to grow at about 40% annually. This trend now exceeds the device capacity growth rate of all existing commercial scale media types including HDD, Flash, Tape and Optical, and the gap between growth rates is about 20%. That implies that the datacenter footprint for storage will be approximately doubling every 3.5 years just to keep up. However, the roadmaps for ongoing density improvement makes the situation much more stark.

The industry needs a new storage medium that is more dense, durable, sustainable, and cost effective to cope with the expected future growth of archival data. DNA, nature’s data storage medium, enters this picture at a time when synthesis and sequencing technologies for advanced medical and scientific applications are enabling the manipulation of synthetic DNA in ways previously unimagined. This session will provide and overview of why DNA data storage is compelling and what the DNA Data Storage Alliance is doing to help build an interoperable DNA Data Storage ecosystem.

Using synthetic DNA for data storage implies two complex steps of digital data processing, namely Encoding and Decoding, which are very different from what we are used to in the conventional Flash environment. Because of the intrinsic statistical behavior of the DNA storage errors (i.e. insertions, deletions, and substitutions), a simulator is required for figuring out the impact of different Encoding/Decoding strategies and algorithms on the storage capabilities of DNA.