Bug 218770 - fsck seems unable to solve corruption
Summary: fsck seems unable to solve corruption
Status: RESOLVED CODE_FIX
Alias: None
Product: File System
Classification: Unclassified
Component: f2fs (show other bugs)
Hardware: All Linux
: P3 high
Assignee: Default virtual assignee for f2fs
URL:
Keywords:
: 218769 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-04-24 11:40 UTC by Guido
Modified: 2024-04-29 15:58 UTC (History)
2 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
fsck (1.89 MB, text/plain)
2024-04-24 11:41 UTC, Guido
Details

Description Guido 2024-04-24 11:40:11 UTC
After installing kernel 6.9rc5 it seems that all my f2fs partitions are corrupted, according to fsck. On boot the check-repair is always performed. I also tried running f2fs from a live usb (with kernel 6.6) but the problem is not solved. Even running fsck several times always finds problems.

I attach the output of fsck -f -d 1 on one of the partitions.
Comment 1 Guido 2024-04-24 11:41:06 UTC
Created attachment 306205 [details]
fsck
Comment 2 Artem S. Tashkinov 2024-04-24 12:19:55 UTC
*** Bug 218769 has been marked as a duplicate of this bug. ***
Comment 3 Artem S. Tashkinov 2024-04-24 12:22:17 UTC
> Even running fsck several times always finds problems.

This looks like a f2fs fsck issue, not the kernel issue.

Please post here:

https://github.com/jaegeuk/f2fs-tools
Comment 4 Artem S. Tashkinov 2024-04-24 12:25:25 UTC
On 4/24/24 12:21 PM, Tor Vic wrote:
> 
> I can confirm the constant fsck issue, and it was fixed in my case by 
> the following patch:
>
>
> https://lore.kernel.org/linux-f2fs-devel/20240409203411.1885121-3-jaegeuk@kernel.org/
Comment 5 Guido 2024-04-24 12:30:47 UTC
(In reply to Artem S. Tashkinov from comment #4)
> On 4/24/24 12:21 PM, Tor Vic wrote:
> > 
> > I can confirm the constant fsck issue, and it was fixed in my case by 
> > the following patch:
> >
> >
> >
> https://lore.kernel.org/linux-f2fs-devel/20240409203411.1885121-3-jaegeuk@kernel.org/

I have 6.9.rc5 (dated 2024-04-21 on kernel.org) Is that patch already applied to it? If yes, it doesn't solve the bug.
Comment 6 Jaegeuk Kim 2024-04-24 17:30:59 UTC
Thank you for the report. It seems I need to reapply that patch indeed.
Comment 7 Guido 2024-04-29 15:58:20 UTC
(In reply to Jaegeuk Kim from comment #6)
> Thank you for the report. It seems I need to reapply that patch indeed.

Does rc6 contain the reapplied patch?

Note You need to log in before you can comment on or make changes to this bug.