linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: guo weichao <guoweichao@msn.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] 回复:  [PATCH] fsck.f2fs: write checkpoint with OPU mode
Date: Mon, 24 Jun 2019 10:24:16 +0800	[thread overview]
Message-ID: <efdf67e2-74d4-bc6d-2ad3-f9b2d308fcff@huawei.com> (raw)
In-Reply-To: <MWHPR02MB26710762B08C9EAB74BB2FABC6E00@MWHPR02MB2671.namprd02.prod.outlook.com>

Hi Jaegeuk,

I picked up Weichao's patch since I'm not sure whether Weichao still has time
working on it.

On 2019/6/24 9:23, guo weichao wrote:
> Hi Jaegeuk,
> 
> I think it's better to copy CP A to CP B position first, which can make sure we
> have a fsck-not-touched correct checkpoint. 

Jaegeuk, Weichao,

I think it's okay, let me update the patch. :)

> 
> P.S: did you want to discuss it with Chao Yu? :)HAHA

Weichao, it's glad to see your activity again. ;)

Thanks,

> 
> BR,
> Weichao
> --------------------------------------------------------------------------------
> *发件人:* Jaegeuk Kim <jaegeuk@kernel.org>
> *发送时间:* 2019年6月23日 5:46
> *收件人:* Chao Yu
> *抄送:* linux-f2fs-devel@lists.sourceforge.net
> *主题:* Re: [f2fs-dev] [PATCH] fsck.f2fs: write checkpoint with OPU mode
>  
> Hi Weichao,
> 
> This patch breaks the image found by my local power-cut tests.
> 
> On 05/24, Chao Yu wrote:
>> This original patch was from Weichao Guo.
>> 
>> We may encounter both checkpoints invalid in such a case:
>> 1. kernel writes CP A;
>> 2. power-cut when kernel writes CP B, then CP B is corrupted;
>> 3. fsck: load CP A, fix meta/data;
> 
> Would it be better to copy CP A to CP B position first?
> 
> Thanks,
> 
>> 4. power-cut when fsck writes CP A in-place, then CP A is corrupted too;
>> 
>> To avoid both checkpoints being invalid, this patch changes to enables
>> fsck to write checkpoint with out-place-update method first, and then
>> write checkpoint in original place.
>> 
>> This can make sure during fsck repairing, even there is sudden power-cut,
>> filesystem will still have at least one valid checkpoint.
>> 
>> Signed-off-by: Weichao Guo <guoweichao@huawei.com>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> v2:
>> - clean up codes
>> - cover flush_journal_entries() case
>> - update commet message
>>  fsck/fsck.c  | 17 +++++++++++++++--
>>  fsck/fsck.h  |  1 +
>>  fsck/mount.c | 15 ++++++++++++++-
>>  3 files changed, 30 insertions(+), 3 deletions(-)
>> 
>> diff --git a/fsck/fsck.c b/fsck/fsck.c
>> index 6f0f262..6aed51d 100644
>> --- a/fsck/fsck.c
>> +++ b/fsck/fsck.c
>> @@ -2121,6 +2121,19 @@ static void fix_checkpoint(struct f2fs_sb_info *sbi)
>>                write_nat_bits(sbi, sb, cp, sbi->cur_cp);
>>  }
>>  
>> +static void fix_checkpoints(struct f2fs_sb_info *sbi)
>> +{
>> +     int i, ret;
>> +
>> +     for (i = 0; i < 2; i++) {
>> +             /* write checkpoint out of place first */
>> +             sbi->cur_cp = sbi->cur_cp % 2 + 1;
>> +             fix_checkpoint(sbi);
>> +             ret = f2fs_fsync_device();
>> +             ASSERT(ret >= 0);
>> +     }
>> +}
>> +
>>  int check_curseg_offset(struct f2fs_sb_info *sbi, int type)
>>  {
>>        struct curseg_info *curseg = CURSEG_I(sbi, type);
>> @@ -2771,10 +2784,10 @@ int fsck_verify(struct f2fs_sb_info *sbi)
>>                        rewrite_sit_area_bitmap(sbi);
>>                        fix_curseg_info(sbi);
>>                        fix_checksum(sbi);
>> -                     fix_checkpoint(sbi);
>> +                     fix_checkpoints(sbi);
>>                } else if (is_set_ckpt_flags(cp, CP_FSCK_FLAG) ||
>>                        is_set_ckpt_flags(cp, CP_QUOTA_NEED_FSCK_FLAG)) {
>> -                     write_checkpoint(sbi);
>> +                     write_checkpoints(sbi);
>>                }
>>        }
>>        return ret;
>> diff --git a/fsck/fsck.h b/fsck/fsck.h
>> index d38e8de..8fe5db1 100644
>> --- a/fsck/fsck.h
>> +++ b/fsck/fsck.h
>> @@ -192,6 +192,7 @@ extern void move_curseg_info(struct f2fs_sb_info *, u64, int);
>>  extern void write_curseg_info(struct f2fs_sb_info *);
>>  extern int find_next_free_block(struct f2fs_sb_info *, u64 *, int, int);
>>  extern void write_checkpoint(struct f2fs_sb_info *);
>> +extern void write_checkpoints(struct f2fs_sb_info *);
>>  extern void update_superblock(struct f2fs_super_block *, int);
>>  extern void update_data_blkaddr(struct f2fs_sb_info *, nid_t, u16, block_t);
>>  extern void update_nat_blkaddr(struct f2fs_sb_info *, nid_t, nid_t, block_t);
>> diff --git a/fsck/mount.c b/fsck/mount.c
>> index 1c5cd93..bbb1af7 100644
>> --- a/fsck/mount.c
>> +++ b/fsck/mount.c
>> @@ -2127,7 +2127,7 @@ void flush_journal_entries(struct f2fs_sb_info *sbi)
>>        int n_sits = flush_sit_journal_entries(sbi);
>>  
>>        if (n_nats || n_sits)
>> -             write_checkpoint(sbi);
>> +             write_checkpoints(sbi);
>>  }
>>  
>>  void flush_sit_entries(struct f2fs_sb_info *sbi)
>> @@ -2452,6 +2452,19 @@ void write_checkpoint(struct f2fs_sb_info *sbi)
>>        ASSERT(ret >= 0);
>>  }
>>  
>> +void write_checkpoints(struct f2fs_sb_info *sbi)
>> +{
>> +     int i, ret;
>> +
>> +     for (i = 0; i < 2; i++) {
>> +             /* write checkpoint out of place first */
>> +             sbi->cur_cp = sbi->cur_cp % 2 + 1;
>> +             write_checkpoint(sbi);
>> +             ret = f2fs_fsync_device();
>> +             ASSERT(ret >= 0);
>> +     }
>> +}
>> +
>>  void build_nat_area_bitmap(struct f2fs_sb_info *sbi)
>>  {
>>        struct curseg_info *curseg = CURSEG_I(sbi, CURSEG_HOT_DATA);
>> -- 
>> 2.18.0.rc1
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


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

  parent reply	other threads:[~2019-06-24  2:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24  7:56 [PATCH] fsck.f2fs: write checkpoint with OPU mode Chao Yu
2019-06-22 21:46 ` [f2fs-dev] " Jaegeuk Kim
     [not found]   ` <MWHPR02MB26710762B08C9EAB74BB2FABC6E00@MWHPR02MB2671.namprd02.prod.outlook.com>
2019-06-24  2:24     ` Chao Yu [this message]
2019-06-24 14:36       ` [f2fs-dev] 回复: " Chao Yu
2019-06-24 16:02         ` Jaegeuk Kim
2019-06-25  1:59           ` 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=efdf67e2-74d4-bc6d-2ad3-f9b2d308fcff@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=guoweichao@msn.com \
    --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).