1 / 6

Enhancing NTFS for SSD Compatibility: A New Approach to Flash Memory Management

As SSDs become the primary storage devices in PCs, the traditional NTFS behavior may not optimally support flash memory, particularly regarding metadata file handling. SSDs can experience performance degradation due to large RAM consumption and a high frequency of small writes. To address these limitations, a transformation scheme in the Flash Translation Layer (FTL) is necessary, incorporating log-based mechanisms and facilitating sequential access. We also explore YAFFS and JFFS2 file systems along with their constraints, aiming for a robust solution that enhances fast mount times and simplifies recovery processes.

carl
Télécharger la présentation

Enhancing NTFS for SSD Compatibility: A New Approach to Flash Memory Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Motivation • SSDs will become the primary storage devices on PC, but NTFS behavior may not suitable to flash memory especially on metadata files. • When considering the ram consumption, the mapping unit of the SSDs may become large; this situation will degrade the performance since there are a lot of small writes come from metadata files access. • Design a transformation scheme in FTL to make the NTFS behavior compatible to SSDs. • Log-based mechanism and sequential access on flash memory. • Fast mount time and easy to recover.

  2. YAFFS • Every file has a file id, which is 18 bits. • File data is stored in chunks, which is the same size as flash page. • Chunk 0 is used to store file header. • Each flash contains file id and chunk number, which is 20 bits, in the spare area. • Each page contains 2-bit serial number for crash-recovery.

  3. YAFFS Slot = file id % 256 Hash Link

  4. JFFS2 • JFFS is a log-structured file system for NOR flash memory. • Changes to files and directories are "logged" to flash in nodes, of which there are two types: • inodes: a header with file metadata, followed by the file data (if any). A file can correspond to mulipleinodes. • dirent nodes: directory entries each holding a name and an inode number.

  5. Disadvantages of YAFFS and JFFS • When mounting the device, each page need to be scanned to establish the whole file system information. • There are a lot of structure need to be maintained in the ram, such as inodes, yaffs_objects. • They are both designed for embedded system, so there are a lot of limitations in the file system, such as file size, number of files. • They all need to mark invalid pages, which is not allowed in MLC flash.

  6. Ext2/3 File system layout • When modifying a file, file system need to update group descriptor table, block bitmap, inode bitmap, inode table, and journaling blocks; all of these accesses are small writes and go fixed location in the file system. File system journaling

More Related