From: Yunlei He <heyunlei@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Cc: zhangdianfang@huawei.com
Subject: [PATCH] fsck.f2fs: recover nat bits feature default by fsck
Date: Mon, 9 Apr 2018 11:34:41 +0800 [thread overview]
Message-ID: <1523244881-13125-1-git-send-email-heyunlei@huawei.com> (raw)
Now, nat bits feature is enabled by default, we will
meet with the following scenarios:
i. disabled, without CP_NAT_BITS_FLAG, if fsck find some
fs errors, fix or write new checkpoint will then enable it.
ii. enabled, with CP_NAT_BITS_FLAG, in the case of sudden
power off, bitmap will get lost but CP_NAT_BITS_FLAG
still exist, fsck will recover bitmap in f2fs_do_mount.
iii. enabled, with CP_NAT_BITS_FLAG, both of bitmap and
CP_NAT_BITS_FLAG will get lost if not enough space for
nat bits or nat bits check failed during mounting.
SBI_NEED_FSCK is set, fsck will recover flag and bitmap
before next mount.
SBI_NEED_FSCK means fs is corrupted, is not suitable for
nat bits disabled. This patch try to recover nat bits all
by fsck, no need set SBI_NEED_FSCK flag in kernel.
Signed-off-by: Yunlei He <heyunlei@huawei.com>
---
fsck/mount.c | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/fsck/mount.c b/fsck/mount.c
index e5574c5..2361ee0 100644
--- a/fsck/mount.c
+++ b/fsck/mount.c
@@ -2389,7 +2389,7 @@ int f2fs_do_mount(struct f2fs_sb_info *sbi)
}
/* Check nat_bits */
- if (c.func != DUMP && is_set_ckpt_flags(cp, CP_NAT_BITS_FLAG)) {
+ if (c.func != DUMP) {
u_int32_t nat_bits_bytes, nat_bits_blocks;
__le64 *kaddr;
u_int32_t blk;
@@ -2406,10 +2406,15 @@ int f2fs_do_mount(struct f2fs_sb_info *sbi)
kaddr = malloc(PAGE_SIZE);
ret = dev_read_block(kaddr, blk);
ASSERT(ret >= 0);
- if (*kaddr != get_cp_crc(cp))
- write_nat_bits(sbi, sb, cp, sbi->cur_cp);
- else
- MSG(0, "Info: Found valid nat_bits in checkpoint\n");
+ if(is_set_ckpt_flags(cp, CP_NAT_BITS_FLAG)) {
+ if (*kaddr != get_cp_crc(cp))
+ write_nat_bits(sbi, sb, cp, sbi->cur_cp);
+ else
+ MSG(0, "Info: Found valid nat_bits in checkpoint\n");
+ } else if (c.func == FSCK){
+ ASSERT_MSG("Need to recover nat_bits.");
+ c.fix_on = 1;
+ }
free(kaddr);
}
return 0;
--
1.9.1
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2018-04-09 3:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 3:34 Yunlei He [this message]
2018-04-09 10:59 ` [PATCH] fsck.f2fs: recover nat bits feature default by fsck Chao Yu
2018-04-10 4:00 ` Jaegeuk Kim
2018-04-10 4:26 ` heyunlei
2018-04-13 0:37 ` Jaegeuk Kim
2018-04-13 1:20 ` Chao Yu
2018-04-13 3:59 ` Jaegeuk Kim
2018-04-13 7:37 ` Chao Yu
2018-04-10 8:58 ` heyunlei
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=1523244881-13125-1-git-send-email-heyunlei@huawei.com \
--to=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
--cc=zhangdianfang@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).