From: Gustavo Brondani Schenkel <gustavo.schenkel@gmail.com>
To: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [f2fs-dev] Issue with f2fs on kernel 6.9.x
Date: Mon, 27 May 2024 18:57:52 -0300 [thread overview]
Message-ID: <bf02d65d-876f-4a90-84b5-595707659fb0@gmail.com> (raw)
In-Reply-To: <2024052527-panama-playgroup-899a@gregkh>
Hi,
since upgrade to Kernel 6.9 I am getting Issues when booting using f2fs.
If I am correct, I am receiving `fs error: invalid_blkaddr` in two
distinct drives, one nvme, and other sata.
Each reboot the fsck runs to correct this suppose error.
If I downgrade to Kernel 6.6.29, on the first boot, fsck runs just once,
than after reboot is normal.
I used 6.9.0, but in 6.9.1 it took my attention because I don't reboot
often. One 6.9.2 the Issue persist.
Since I didn't find nothing about issues on kernel messages I am trying
reach you.
I use Slackware Linux 15.0-current, and debug flags are disabled by
default, but if you needed,
I can rebuilt the kernel with the flags you say are needed, to find what
are happening.
PS: I didn't find any better way to report this issue, said that, sorry
if this is the wrong way to do so.
--
Gustavo B. Schenkel
System Analyst
B.Sc(IT), MBA(Banking)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next parent reply other threads:[~2024-05-28 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024052527-panama-playgroup-899a@gregkh>
2024-05-27 21:57 ` Gustavo Brondani Schenkel [this message]
2024-05-28 1:24 ` [f2fs-dev] Issue with f2fs on kernel 6.9.x Jaegeuk Kim
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=bf02d65d-876f-4a90-84b5-595707659fb0@gmail.com \
--to=gustavo.schenkel@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).