From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 218870] F2FS mount/unmount results in invalid_blkaddr
Date: Thu, 23 May 2024 13:13:35 +0000 [thread overview]
Message-ID: <bug-218870-202145-voB1yIJkJ6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218870-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218870
Paul Gover (pmw.gover@yahoo.co.uk) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmw.gover@yahoo.co.uk
--- Comment #2 from Paul Gover (pmw.gover@yahoo.co.uk) ---
I can confirm the problem on my Gentoo system with a custom kernel.
As above, with the 6.8.9 kernel , no problems, but with the 6.9.1 kernel (same
configuration apart from a couple of new items resulting from "make oldconfig")
I get the invalid_blkaddr message and a full fsck. That full fsck fails to fix
the problem, so the long boot occurs on all subsequent boots.
In my case I'm running "fsck.f2fs -f /dev/nvme0n1p3" from a shell script in my
home-rolled initramfs, using sys-fs/f2fs-tools-1.16.0-r1.
I'll put my log in an attachment.
--
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
next prev parent reply other threads:[~2024-05-23 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 21:01 [f2fs-dev] [Bug 218870] New: F2FS mount/unmount results in invalid_blkaddr bugzilla-daemon
2024-05-21 21:35 ` [f2fs-dev] [Bug 218870] " bugzilla-daemon
2024-05-23 13:13 ` bugzilla-daemon [this message]
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-voB1yIJkJ6@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.