You are not logged in.
Pages: 1
How do I find out what F2FS is doing every boot-up? Ever since I switched to F2FS, systemd-analyze blame reports 2 mins or more spent in the root fsck. I know that F2FS fsck is slow, but is it expected to be this slow even after clean shutdowns. How can I speed this up?
Output from systemd-analyze, along with my fstab and crypttab.initramfs: https://paste.sr.ht/~ananth/666b3f6ef2a … e1305f37f4
/dev/nvme0n1p2 and /dev/nvme1n1 have LUKS volumes on them which are mounted to /dev/mapper/root0 and /dev/mapper/root1 respectively in initramfs. The root F2FS spans both these volumes.
Offline
Have a look into the journal via `journalctl -b`. It should include the output of f2fsck.
Is every boot-up slow or does it only sometimes take so much time? There were times when f2fsck ran a full check after each kernel update, although this should be a thing of the past (see https://github.com/jaegeuk/f2fs-tools/commit/1126e38 ).
Also there have been similar issues when the f2fs-tools version differs from the used kernel: https://github.com/jaegeuk/f2fs-tools/c … faebbdc78f. Do you use some older kernel version (lts or similar)?
Offline
Pages: 1