Received-SPF: pass (google.com: domain of linux-kernel+bounces-191470-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <bf02d65d-876f-4a90-84b5-595707659fb0@gmail.com>
Date: Mon, 27 May 2024 18:57:52 -0300
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Gustavo Brondani Schenkel <gustavo.schenkel@gmail.com>
Subject: Issue with f2fs on kernel 6.9.x
To: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
 stable@vger.kernel.org
References: <2024052527-panama-playgroup-899a@gregkh>
Content-Language: en-US
In-Reply-To: <2024052527-panama-playgroup-899a@gregkh>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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)