From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH v2 0/4] fsck: Check write pointers of zoned block devices
Date: Mon, 26 Aug 2019 00:10:10 +0000 [thread overview]
Message-ID: <BYAPR04MB5816E9510B8836D734424059E7A10@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: 51daaa42-58b0-85dd-dcda-13185afe5b63@kernel.org
Chao,
On 2019/08/23 22:09, Chao Yu wrote:
> Hi Damien,
>
> Do you have time to take a look at this patch set, and add a reviewed-by if it
> is okay to you. :)
My apologies for not chiming in earlier. Shinichiro works in my group and I
asked him to work on this. We have gone through several iterations internally
and this is the latest version.
So:
Reviewed-by: Damien Le Moal <damien.lemoal@wdc.com>
>
> Thanks,
>
> On 2019-8-21 12:47, Shin'ichiro Kawasaki wrote:
>> On sudden f2fs shutdown, zoned block device status and f2fs meta data can be
>> inconsistent. When f2fs shutdown happens during write operations, write pointers
>> on the device go forward but the f2fs meta data does not reflect write pointer
>> progress. This inconsistency will eventually cause "Unaligned write command"
>> error when restarting write operation after the next mount. This error can be
>> observed with xfstests test case generic/388, which enforces sudden shutdown
>> during write operation and checks the file system recovery. Once the error
>> happens because of the inconsistency, the file system requires fix. However,
>> fsck.f2fs does not have a feature to check and fix it.
>>
>> This patch series adds a new feature to fsck.f2fs to check and fix the
>> inconsistency. First and second patches add two functions which helps fsck to
>> call report zone and reset zone commands to zoned block devices. Third patch
>> checks write pointers of zones that current segments recorded in meta data point
>> to. This covers the failure symptom observed with xfstests. The last patch
>> checks write pointers of zones that current segments do not point to, which
>> covers a potential failure scenario.
>>
>> This patch series depends on other patches for zoned block devices, then it
>> conflicts with the master branch in f2fs-tools.git as of Aug/19/2019. It can be
>> applied without conflict to dev and dev-test branch tips.
>>
>> Changes from v1:
>> * Fixed build failure on dev branch
>>
>> Shin'ichiro Kawasaki (4):
>> libf2fs_zoned: Introduce f2fs_report_zones() helper function
>> libf2fs_zoned: Introduce f2fs_reset_zone() function
>> fsck.f2fs: Check write pointer consistency with current segments
>> fsck.f2fs: Check write pointer consistency with valid blocks count
>>
>> fsck/fsck.c | 161 ++++++++++++++++++++++++++++++++++++++++++++
>> fsck/fsck.h | 3 +
>> fsck/main.c | 2 +
>> include/f2fs_fs.h | 3 +
>> lib/libf2fs_zoned.c | 81 ++++++++++++++++++++++
>> 5 files changed, 250 insertions(+)
>>
>
--
Damien Le Moal
Western Digital Research
_______________________________________________
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-08-26 0:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 4:47 [f2fs-dev] [PATCH v2 0/4] fsck: Check write pointers of zoned block devices Shin'ichiro Kawasaki
2019-08-21 4:47 ` [f2fs-dev] [PATCH v2 1/4] libf2fs_zoned: Introduce f2fs_report_zones() helper function Shin'ichiro Kawasaki
2019-08-27 1:34 ` Chao Yu
2019-08-28 8:32 ` Shinichiro Kawasaki
2019-08-21 4:48 ` [f2fs-dev] [PATCH v2 2/4] libf2fs_zoned: Introduce f2fs_reset_zone() function Shin'ichiro Kawasaki
2019-08-27 1:36 ` Chao Yu
2019-08-21 4:48 ` [f2fs-dev] [PATCH v2 3/4] fsck.f2fs: Check write pointer consistency with current segments Shin'ichiro Kawasaki
2019-08-27 2:01 ` Chao Yu
2019-08-27 2:13 ` Chao Yu
2019-08-29 4:41 ` Shinichiro Kawasaki
2019-08-21 4:48 ` [f2fs-dev] [PATCH v2 4/4] fsck.f2fs: Check write pointer consistency with valid blocks count Shin'ichiro Kawasaki
2019-08-27 2:25 ` Chao Yu
2019-08-28 11:53 ` Shinichiro Kawasaki
2019-08-29 14:42 ` Chao Yu
2019-08-30 7:21 ` Shinichiro Kawasaki
2019-08-23 13:09 ` [f2fs-dev] [PATCH v2 0/4] fsck: Check write pointers of zoned block devices Chao Yu
2019-08-26 0:10 ` Damien Le Moal [this message]
2019-08-26 7:37 ` 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=BYAPR04MB5816E9510B8836D734424059E7A10@BYAPR04MB5816.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.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).