From: Tor Vic via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: guido iodice <guido.iodice@gmail.com>
Cc: aros@gmx.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [Bug 218770] fsck seems unable to solve corruption
Date: Wed, 24 Apr 2024 14:47:30 +0200 [thread overview]
Message-ID: <bda1c8b9-78a8-4232-b4a5-df3193355081@mailbox.org> (raw)
In-Reply-To: <CAL0yVhy5zW1wUAsN1+the3UnkG0cy84B9nXEWUZDOVN=Q2+tDw@mail.gmail.com>
On 4/24/24 14:42, guido iodice wrote:
> Thank you.
>
> For clarity, can you confirm that this is a false alarm and in fact there
> should be no corruption?
I'm not a developer, but my computer runs just fine with this patch
applied since a week or so.
I didn't notice any data corruption or error messages in the log.
>
> Best
>
> ------------------------
> Guido Iodice
>
>
>
> Il giorno mer 24 apr 2024 alle ore 14:40 Tor Vic <torvic9@mailbox.org> ha
> scritto:
>
>>
>>
>> On 4/24/24 14:30, bugzilla-daemon@kernel.org wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=218770
>>>
>>> --- Comment #5 from Guido (guido.iodice@gmail.com) ---
>>> (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.
>>>
>>
>> No, not applied yet.
>>
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-04-24 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 11:40 [f2fs-dev] [Bug 218770] New: fsck seems unable to solve corruption bugzilla-daemon
2024-04-24 11:41 ` [f2fs-dev] [Bug 218770] " bugzilla-daemon
2024-04-24 12:19 ` bugzilla-daemon
2024-04-24 12:22 ` bugzilla-daemon
2024-04-24 12:25 ` bugzilla-daemon
2024-04-24 12:30 ` bugzilla-daemon
2024-04-24 12:40 ` Tor Vic via Linux-f2fs-devel
[not found] ` <CAL0yVhy5zW1wUAsN1+the3UnkG0cy84B9nXEWUZDOVN=Q2+tDw@mail.gmail.com>
2024-04-24 12:47 ` Tor Vic via Linux-f2fs-devel [this message]
2024-04-24 17:30 ` bugzilla-daemon
2024-04-29 15:58 ` bugzilla-daemon
2024-05-14 11:41 ` bugzilla-daemon
2024-05-14 16:32 ` bugzilla-daemon
2024-05-17 20:02 ` bugzilla-daemon
2024-05-20 20:08 ` bugzilla-daemon
2024-05-20 21:42 ` bugzilla-daemon
2024-05-25 19:45 ` bugzilla-daemon
2024-05-25 19:46 ` bugzilla-daemon
2024-05-28 16:56 ` bugzilla-daemon
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=bda1c8b9-78a8-4232-b4a5-df3193355081@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).