All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 218870] New: F2FS mount/unmount results in invalid_blkaddr
Date: Tue, 21 May 2024 21:01:51 +0000	[thread overview]
Message-ID: <bug-218870-202145@https.bugzilla.kernel.org/> (raw)

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: filesystem_f2fs@kernel-bugs.kernel.org
          Reporter: patrik.plihal@gmail.com
        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
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2024-05-21 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 21:01 bugzilla-daemon [this message]
2024-05-21 21:35 ` [f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr bugzilla-daemon
2024-05-23 13:13 ` bugzilla-daemon
2024-05-23 13:14 ` bugzilla-daemon
2024-05-24 17:27 ` bugzilla-daemon
2024-05-25 19:45 ` bugzilla-daemon
2024-05-26  8:03 ` bugzilla-daemon
2024-05-28 16:57 ` bugzilla-daemon
2024-05-30 10:48 ` bugzilla-daemon
2024-05-31 23:23 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-218870-202145@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.