[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZlUyMr0FwaT69vgO@google.com>
Date: Tue, 28 May 2024 01:24:02 +0000
From: Jaegeuk Kim <jaegeuk@...nel.org>
To: Gustavo Brondani Schenkel <gustavo.schenkel@...il.com>
Cc: linux-f2fs-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: Issue with f2fs on kernel 6.9.x
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)
>
Powered by blists - more mailing lists