Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In some cases, fsck.f2fs takes very long time > 90s, how to improve ? #23

Open
rockcarry opened this issue Nov 30, 2023 · 1 comment
Open

Comments

@rockcarry
Copy link

rockcarry commented Nov 30, 2023

Test condition:
Allwinner A133 Android 10 tablet.

  • Data partition is formated to f2fs.
  • fsck enabled during android boot
  • 32GB emmc flash, and data partition size is 28GB+

Steps to reproduce:

  1. create 20GB file on data partition:
    belsito:/data # dd if=/dev/urandom of=/data/test.bin bs=1k count=20m 20971520+0 records in 20971520+0 records out 21474836480 bytes (20 G) copied, 679.607325 s, 30 M/s
  2. create 500MB file on data partition:
    dd if=/dev/urandom of=/data/test2.bin bs=1k count=500k
    don't wait this command finish, open another adb shell, type command:
    reboot # this makes device reboot
  3. after reboot fsck.f2fs found data corruption, and took very long time >90s to finish check:

image

@rockcarry
Copy link
Author

Is any way to improve to reduce the check time ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant