F2FS: Difference between revisions
m BOT: Dating templates: {{citation needed}} (1) |
mNo edit summary |
||
Line 24: | Line 24: | ||
}} |
}} |
||
'''F2FS''' is a [[file system]] created by Kim Jaegeuk at [[Samsung]] |
'''F2FS''' is a [[file system]] created by Kim Jaegeuk (hangul: 김재극) at [[Samsung]] for the [[Linux]] operating system kernel.<ref>[https://lkml.org/lkml/2012/10/5/205 LKML: f2fs: introduce flash-friendly file system]</ref> |
||
The motivation for F2FS was to build a file system that from the sketch takes into account the characteristics of [[NAND flash memory]]-based storage devices (such as [[SSD]], [[eMMC]], and [[SecureDigital|SD]] cards), which have been widely being used ranging from mobile to server systems. |
The motivation for F2FS was to build a file system that from the sketch takes into account the characteristics of [[NAND flash memory]]-based storage devices (such as [[SSD]], [[eMMC]], and [[SecureDigital|SD]] cards), which have been widely being used ranging from mobile to server systems. |
Revision as of 12:23, 6 October 2012
Developer(s) | Kim Jaegeuk |
---|---|
Full name | Flash 2 File System[citation needed] |
Introduced | 05 Oct 2012 with Linux 3.6 |
Other | |
Supported operating systems | Linux |
F2FS is a file system created by Kim Jaegeuk (hangul: 김재극) at Samsung for the Linux operating system kernel.[1]
The motivation for F2FS was to build a file system that from the sketch takes into account the characteristics of NAND flash memory-based storage devices (such as SSD, eMMC, and SD cards), which have been widely being used ranging from mobile to server systems.
Samsung chose a log structure file system approach, which adapted to the new forms of storage. Also they remedied some known issues of the very old log structured file system, such as snowball effect of wandering tree and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme aka FTL, Samsung also adds various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.