That's not correct. It was designed for SSD, NVMe and the like by people from Samsung, who make quite a lot of that stuff. It has some issues that can be mitigated (note that if you apply their changes, they need the filesystem formatted with the "extra_attr" flag, which breaks grub's ability to read it).Ionen wrote:...
Note that F2FS is mostly useful for "dumb" flash storage (like a usb thumbdrive), any remotely modern SSDs don't need this.



IIUC F2FS is, like ext4, a journalling filesystem. So presumably after a power failure it's a case of replaying the journal for both ext4 and f2fs.eccerr0r wrote:Especially SATA SSDs are "cooked" interfaces and deal with wear leveling automatically so there's no need to run a flash centric filesystem.
When they start forcing us to use "WinSSS" (aka solid state storage with the "Winmodem" moniker) then perhaps we need to start using f2fs of some sort, and waste CPU cycles/memory to deal with wear leveling and block allocation. But even so, unless you have some sort of power guarantee (battery or at least some capacitor backup) there's a high risk for corruption if you can't finish metadata writes. SATA SSDs will detect power failures and clean up before going dark, something that you can't guarantee with F2FS on solely line power.

Still can't guarantee atomic writes when power is unreliable. Even mechanical hard drives have "last gasp" writes for when power goes out, no guarantees when doing in software.Goverp wrote:IIUC F2FS is, like ext4, a journalling filesystem. So presumably after a power failure it's a case of replaying the journal for both ext4 and f2fs.



Code: Select all
0100100100100000011000010110110100100000
0100111001100001010011100010000100100000
0100100100100000011000010110110100100000
0110000100100000011011010110000101101110
00100001


Similar.CooSee wrote:i only use 'xfs' and never disappointed me, even after 'power outage'.

Yeah,asturm wrote:ext4. boring fs is best fs.