From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] fsck.f2fs: write checkpoint with OPU mode
Date: Wed, 17 Jul 2019 09:25:02 +0800 [thread overview]
Message-ID: <afabbf0f-3b69-80dd-fd89-ede1bafd997f@huawei.com> (raw)
In-Reply-To: <20190716210857.GA5347@jaegeuk-macbookpro.roam.corp.google.com>
On 2019/7/17 5:08, Jaegeuk Kim wrote:
> On 07/16, Chao Yu wrote:
>> Ping,
>
> It seems this is still breaking the tests. At some point on fault/power tests,
> I hit fsck is stopped since it's missing one NAT node.
>
>>
>> On 2019-6-26 17:48, Chao Yu wrote:
>>> + ret = dev_read(buf, src << F2FS_BLKSIZE_BITS, seg_size);
>>> + ASSERT(ret >= 0);
>>> +
>>> + ret = dev_write(buf, dst << F2FS_BLKSIZE_BITS, seg_size);
>>> + ASSERT(ret >= 0);
My bad, it looks seg_size is wrong, let me send v3...
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2019-07-17 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 9:48 [f2fs-dev] [PATCH v2] fsck.f2fs: write checkpoint with OPU mode Chao Yu
2019-07-16 14:25 ` Chao Yu
2019-07-16 21:08 ` Jaegeuk Kim
2019-07-17 1:25 ` Chao Yu [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=afabbf0f-3b69-80dd-fd89-ede1bafd997f@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).