New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 780162 link

Starred by 4 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

investigate using f2fs for stateful partition

Project Member Reported by gwendal@chromium.org, Oct 31 2017

Issue description

f2fs has been design from the ground up for SSD device. It has been designed to improve SSD lifespan.
The f2fs maintainer is now at Google, Jaegeuk Kim (jaegeuk@)

f2fs vs ext4 performance on 4.12 are similar: http://openbenchmarking.org/result/1705203-TR-LINUX412F50&obr_imw=y


To install new machine with f2fs stateful partition, we need to make several changes: 
- chromeos-installer: initial installation
- chromeos-init: mount, clobber
- cryptohome: normally no change are required, as ioctls for directory encryption are identical, verify there is no assumption ext4 is the underlying filesystem
- ARC++ 
- everywhere tunefs is used.
 
 
Cc: adlr@chromium.org xiaochu@chromium.org sonnyrao@chromium.org mnissler@chromium.org ahass...@chromium.org briannorris@chromium.org semenzato@chromium.org jorgelo@chromium.org gwendal@chromium.org
 Issue 800569  has been merged into this issue.

Comment 2 by jaegeuk@google.com, Jan 12 2018

Very interesting! Both Pixel 2018 and Android Go adopted F2FS for /userdata, so let me know, if anyone is interested in F2FS. :)

Sign in to add a comment