linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Tor Vic via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: guido.iodice@gmail.com, aros@gmx.com
Subject: Re: [f2fs-dev] [Bug 218769] New: fsck seems unable to solve corruption
Date: Wed, 24 Apr 2024 14:21:39 +0200	[thread overview]
Message-ID: <ac903336-0d00-4cfa-b09c-6f99b709af53@mailbox.org> (raw)
In-Reply-To: <bug-218769-202145@https.bugzilla.kernel.org/>



On 4/24/24 13:38, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218769
> 
>              Bug ID: 218769
>             Summary: fsck seems unable to solve corruption
>             Product: File System
>             Version: 2.5
>            Hardware: All
>                  OS: Linux
>              Status: NEW
>            Severity: high
>            Priority: P3
>           Component: f2fs
>            Assignee: filesystem_f2fs@kernel-bugs.kernel.org
>            Reporter: guido.iodice@gmail.com
>          Regression: No
> 
> Created attachment 306204
>    --> https://bugzilla.kernel.org/attachment.cgi?id=306204&action=edit
> fsck
> 
> 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 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 attach the output of fsck -f -d 1 on one of the partitions.
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2024-04-24 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 11:38 [f2fs-dev] [Bug 218769] New: fsck seems unable to solve corruption bugzilla-daemon
2024-04-24 12:19 ` [f2fs-dev] [Bug 218769] " bugzilla-daemon
2024-04-24 12:21 ` Tor Vic via Linux-f2fs-devel [this message]

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=ac903336-0d00-4cfa-b09c-6f99b709af53@mailbox.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=aros@gmx.com \
    --cc=guido.iodice@gmail.com \
    --cc=torvic9@mailbox.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).