https://bugzilla.kernel.org/show_bug.cgi?id=218870
Bug ID: 218870
Summary: F2FS mount/unmount results in invalid_blkaddr
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: f2fs
Assignee: [email protected]
Reporter: [email protected]
Regression: No
At least 3 people hit an issue with f2fs mount taking a long time (due to
fsck).
In 2 cases it's is the boot partition which delays boot time, in my case it
simply delays a mount.
I prepared a example to reproduce the invalid_blkaddr (and which I presume is
the root cause for the long-mount/fsck)
1. dd if=/dev/zero of=test.img count=100 bs=1M
2. mkfs.f2fs -f ./test.img
3. fsck.f2fs test.img | grep errors # nothing
4. mount -t f2fs ./test.img ./mnt
5. umount ./test.img
6. fsck.f2fs test.img | grep errors
# Info: fs errors: invalid_blkaddr
my initial comment / analysis started here:
https://bbs.archlinux.org/viewtopic.php?pid=2172855#p2172855
Linux blackbox 6.9.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 17 May 2024 16:56:38
+0000 x86_64 GNU/Linux
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
