From: Chao Yu <chao@kernel.org>
To: Ju Hyung Park <qkrwngud825@gmail.com>, Chao Yu <yuchao0@huawei.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v3 2/2] f2fs-tools: relocate chksum_offset for large_nat_bitmap feature
Date: Sun, 19 May 2019 13:09:06 +0800 [thread overview]
Message-ID: <0f89b0b6-5cc5-6618-72e5-8a2f81947161@kernel.org> (raw)
In-Reply-To: <CAD14+f1+puy4M6rL_SbGt9vej=7LgK+qEjq71_878=oqSvjJ2Q@mail.gmail.com>
Hi Ju Hyung,
On 2019-5-19 4:09, Ju Hyung Park wrote:
> Hey Chao,
>
> Sorry for the late reply.
>
> On Wed, May 15, 2019 at 6:23 PM Chao Yu <yuchao0@huawei.com> wrote:
>> So I doubt that sit version bitmap is corrupted, could you add below log and
>> reproduce this issue?
>
> Just done it. The logs are at http://arter97.com/f2fs/v3__/
I've found one bug when repairing cp_payload blocks, could you try it?
[PATCH] fsck.f2fs: fix to repair cp_loads blocks at correct position
Thanks,
>
> Thanks :)
>
>
> _______________________________________________
> 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:[~2019-05-19 5:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 9:33 [PATCH v3 1/2] f2fs-tools: allow unfixed f2fs_checkpoint.checksum_offset Chao Yu
2019-05-14 9:33 ` [PATCH v3 2/2] f2fs-tools: relocate chksum_offset for large_nat_bitmap feature Chao Yu
[not found] ` <CAD14+f2ckNUv9n-Zb9UL_ojX8=24tYBhT-SsrcpVNogqee2tkA@mail.gmail.com>
2019-05-14 9:43 ` Chao Yu
[not found] ` <CAD14+f3NHosrL=5UOBSMbFxQ91x-AuWOj_w=JYkJSnmfDgTkvA@mail.gmail.com>
2019-05-15 4:50 ` Ju Hyung Park
2019-05-15 9:23 ` Chao Yu
2019-05-18 20:09 ` Ju Hyung Park
2019-05-19 5:09 ` Chao Yu [this message]
2019-05-19 9:19 ` Ju Hyung Park
2019-05-19 15:09 ` Chao Yu
2019-06-03 15:23 ` Ju Hyung Park
2019-06-03 20:27 ` Jaegeuk Kim
2019-06-04 1:48 ` Chao Yu
2019-06-27 9:12 ` [f2fs-dev] " Ju Hyung Park
2019-06-27 10:20 ` Chao Yu
2019-07-01 6:23 ` Ju Hyung Park
2019-07-01 9:43 ` Chao Yu
2019-07-05 18:31 ` Jaegeuk Kim
2019-07-06 1:39 ` Chao Yu
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=0f89b0b6-5cc5-6618-72e5-8a2f81947161@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=qkrwngud825@gmail.com \
--cc=yuchao0@huawei.com \
/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).