Reliability mechanisms for file systems using non-volatile memory as a metadata store

Greenan, Kevin M.; Miller, Ethan L.

doi:10.1145/1176887.1176913

Cited by 9 publications

(4 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A simple and common method to avoid protection issues is to mark pages as read-only while mapping them into virtual address space and marking only the pages to be updated as writable when a write is issued. One possible solution [43] is to explore a combination of the EVENODD error correction code algorithm and memory protection to improve the security of storage systems. In that solution, pages are locked for read-only purposes, and are only unlocked when a write is explicitly issued.…”

Section: ) Memory Protectionmentioning

confidence: 99%

Non-Volatile Memory File Systems: A Survey

et al. 2019

View full text Add to dashboard Cite

For decades, computer architectures have treated memory and storage as separate entities. Nowadays, we watch the emergence of new memory technologies that promise to significantly change the landscape of memory systems. Byte-addressable non-volatile memory (NVM) technologies are expected to offer access latency close to that of dynamic random access memory and capacity suited for storage, resulting in storage-class memory. However, they also present some limitations, such as limited endurance and asymmetric read and write latency. Furthermore, adjusting the current hardware and software architectures to embrace these new memories in all their potential is proving to be a challenge in itself. In this paper, recent studies are analyzed to map the state-of-the-art of NVM file systems research. To achieve this goal, over 100 studies related to NVM systems were selected, analyzed, and categorized according to their topics and contributions. From the information extracted from these papers, we derive the main concerns and challenges currently being studied and discussed in the academia and industry, as well as the trends and solutions being proposed to address them.

show abstract

Section: ) Memory Protectionmentioning

confidence: 99%

Non-Volatile Memory File Systems: A Survey

et al. 2019

View full text Add to dashboard Cite

show abstract

“…All data must be copied for a migration because it is incompatible with other file system. In work [24], file system metadata is stored in MRAM in a special designed structure and layout to accelerate the performance. A similar work is done by using NVM and Flash memory store metadata and file data respectively [28].…”

Section: Related Workmentioning

confidence: 99%

FSMAC: A file system metadata accelerator with non-volatile memory

Chen

Wei

Chen

et al. 2013

2013 IEEE 29th Symposium on Mass Storage Systems and Technologies (MSST)

View full text Add to dashboard Cite

File system performance is dominated by metadata access because it is small and popular. Metadata is stored as block in the file system. Partial metadata update results in whole block read and write which amplifies disk I/O. Huge performance gap between CPU and disk aggravates this problem. In this paper, a file system metadata accelerator (referred as FSMAC) is proposed to optimize metadata access by efficiently exploiting the advantages of Nonvolatile Memory (NVM). FSMAC decouples data and metadata I/O path, putting data on disk and metadata on NVM at runtime. Thus, data is accessed in block from I/O bus and metadata is accessed in byte-addressable manner from memory bus. Metadata access is significantly accelerated and metadata I/O is eliminated because metadata in NVM is not flushed back to disk periodically anymore. A light-weight consistency mechanism combining fine-grained versioning and transaction is introduced in the FSMAC. The FSMAC is implemented on the basis of Linux Ext4 file system and intensively evaluated under different workloads. Evaluation results show that the FSMAC accelerates file system up to 49.2 times for synchronized I/O and 7.22 times for asynchronized I/O.

show abstract

“…In addition to providing on-demand error correction, RCFFS can also provide a consistency checker to correct permanent errors during system idle time [22,10]. Because the algebraic signature and Reed-Solomon code use the same underlying Galois field, the operations of taking the algebraic signature of a set of blocks and combining them via XOR or ReedSolomon commute: if f k (D0, D1, . .…”

Section: Reliabilitymentioning

confidence: 99%

Adding aggressive error correction to a high-performance compressing flash file system

Kang

Miller

2009

Proceedings of the Seventh ACM International Conference on Embedded Software

Self Cite

View full text Add to dashboard Cite

While NAND flash memories have rapidly increased in both capacity and performance and are increasingly used as a storage device in many embedded systems, their reliability has decreased both because of increased density and the use of multi-level cells (MLC). Current MLC technology only specifies the minimum requirement for an error correcting code (ECC), but provides no additional protection in hardware. However, existing flash file systems such as YAFFS and JFFS2 rely upon ECC to survive small numbers of bit errors, but cannot survive the larger numbers of bit errors or page failures that are becoming increasingly common as flash file systems scale to multiple gigabytes.We have developed a flash memory file system, RCFFS, that increases reliability by utilizing algebraic signatures to validate data and Reed-Solomon codes to correct erroneous or missing data. Our file system allows users to adjust the level of reliability they require by specifying the number of redundancy pages for each erase block, allowing them to dynamically trade off reliability and storage overhead. By integrating error mitigation with advanced features such as fast mounting and compression, we show, via simulation in NANDsim, that our file system can outperform YAFFS and JFFS2 while surviving flash memory errors that would cause data loss for existing flash file systems.

show abstract

Reliability mechanisms for file systems using non-volatile memory as a metadata store

Cited by 9 publications

References 15 publications

Non-Volatile Memory File Systems: A Survey

Non-Volatile Memory File Systems: A Survey

FSMAC: A file system metadata accelerator with non-volatile memory

Adding aggressive error correction to a high-performance compressing flash file system

Contact Info

Product

Resources

About