From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Gustavo Brondani Schenkel <gustavo.schenkel@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Issue with f2fs on kernel 6.9.x
Date: Tue, 28 May 2024 01:24:02 +0000 [thread overview]
Message-ID: <ZlUyMr0FwaT69vgO@google.com> (raw)
In-Reply-To: <bf02d65d-876f-4a90-84b5-595707659fb0@gmail.com>
Hi,
We're aware of this issue, and the potential fix [1] was merged in 6.9.3-rc1 in
https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#t
Could you please check that patch addresses your problem?
[1] https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#mfd878849ed6dd660ca22aec9ca1a8eb31bc11f0c
Thanks,
On 05/27, Gustavo Brondani Schenkel wrote:
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Gustavo Brondani Schenkel <gustavo.schenkel@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Issue with f2fs on kernel 6.9.x
Date: Tue, 28 May 2024 01:24:02 +0000 [thread overview]
Message-ID: <ZlUyMr0FwaT69vgO@google.com> (raw)
In-Reply-To: <bf02d65d-876f-4a90-84b5-595707659fb0@gmail.com>
Hi,
We're aware of this issue, and the potential fix [1] was merged in 6.9.3-rc1 in
https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#t
Could you please check that patch addresses your problem?
[1] https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#mfd878849ed6dd660ca22aec9ca1a8eb31bc11f0c
Thanks,
On 05/27, Gustavo Brondani Schenkel wrote:
> 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)
>
next prev parent reply other threads:[~2024-05-28 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 14:51 Linux 6.9.2 Greg Kroah-Hartman
2024-05-25 14:51 ` Greg Kroah-Hartman
2024-05-27 21:57 ` [f2fs-dev] Issue with f2fs on kernel 6.9.x Gustavo Brondani Schenkel
2024-05-27 21:57 ` Gustavo Brondani Schenkel
2024-05-28 1:24 ` Jaegeuk Kim [this message]
2024-05-28 1:24 ` 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=ZlUyMr0FwaT69vgO@google.com \
--to=jaegeuk@kernel.org \
--cc=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 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.