All of lore.kernel.org
 help / color / mirror / Atom feed
From: JackieLiu <liuyun01@kylinos.cn>
To: songliubraving@fb.com
Cc: liuzhengyuan@kylinos.cn, linux-raid@vger.kernel.org,
	JackieLiu <liuyun01@kylinos.cn>
Subject: [PATCH 4/4] md/raid5-cache: adjust the write position of the empty block and mark it as a checkpoint
Date: Mon, 28 Nov 2016 16:19:21 +0800	[thread overview]
Message-ID: <20161128081921.5641-4-liuyun01@kylinos.cn> (raw)
In-Reply-To: <20161128081921.5641-1-liuyun01@kylinos.cn>

When recovery is complete, we write an empty block and record his
position first, then make the data-only stripes rewritten done,
the location of the empty block as the last checkpoint position
to write into the super block. And we should update last_checkpoint
to this empty block position.

------------------------------------------------------------------
|  old log       | empty block | data only stripes | invalid log |
------------------------------------------------------------------
^                ^                                 ^
|                |- log->last_checkpoint           |- log->log_start
|                |- log->last_cp_seq               |- log->next_checkpoint
|- log->seq=n    |- log->seq=10+n

At the same time, if there is no data-only stripes, this scene may appear,
| meta1 | meta2 | meta3 |
meta 1 is valid, meta 2 is invalid. meta 3 could be valid. so we should 
The solution is we create a new meta in meta2 with its seq == meta1's 
seq + 10 and let superblock points to meta2. 

Reviewed-by: Zhengyuan Liu <liuzhengyuan@kylinos.cn>
Signed-off-by: JackieLiu <liuyun01@kylinos.cn>
---
 drivers/md/raid5-cache.c | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
index 9e72180..20594f7 100644
--- a/drivers/md/raid5-cache.c
+++ b/drivers/md/raid5-cache.c
@@ -2072,7 +2072,6 @@ r5c_recovery_rewrite_data_only_stripes(struct r5l_log *log,
 		return -ENOMEM;
 	}
 
-	ctx->seq += 10;
 	list_for_each_entry_safe(sh, next, &ctx->cached_list, lru) {
 		struct r5l_meta_block *mb;
 		int i;
@@ -2132,6 +2131,7 @@ static int r5l_recovery_log(struct r5l_log *log)
 	struct mddev *mddev = log->rdev->mddev;
 	struct r5l_recovery_ctx ctx;
 	int ret;
+	sector_t pos;
 
 	ctx.pos = log->last_checkpoint;
 	ctx.seq = log->last_cp_seq;
@@ -2149,6 +2149,10 @@ static int r5l_recovery_log(struct r5l_log *log)
 	if (ret)
 		return ret;
 
+	pos = ctx.pos;
+	r5l_log_write_empty_meta_block(log, ctx.pos, (ctx.seq += 10));
+	ctx.pos = r5l_ring_add(log, ctx.pos, BLOCK_SECTORS);
+
 	if ((ctx.data_only_stripes == 0) && (ctx.data_parity_stripes == 0))
 		pr_debug("md/raid:%s: starting from clean shutdown\n",
 			 mdname(mddev));
@@ -2167,9 +2171,9 @@ static int r5l_recovery_log(struct r5l_log *log)
 
 	log->log_start = ctx.pos;
 	log->next_checkpoint = ctx.pos;
+	log->last_checkpoint = pos;
 	log->seq = ctx.seq;
-	r5l_log_write_empty_meta_block(log, ctx.pos, ctx.seq);
-	r5l_write_super(log, ctx.pos);
+	r5l_write_super(log, pos);
 	return 0;
 }
 
-- 
2.7.4




  parent reply	other threads:[~2016-11-28  8:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  8:19 [PATCH 1/4] md/raid5-cache: remove unnecessary function parameters JackieLiu
2016-11-28  8:19 ` [PATCH 2/4] md/raid5-cache: use ring add to prevent overflow JackieLiu
2016-11-29 20:31   ` Song Liu
2016-11-28  8:19 ` [PATCH 3/4] md/raid5-cache: release the stripe_head at the appropriate location JackieLiu
2016-11-29 20:33   ` Song Liu
2016-11-28  8:19 ` JackieLiu [this message]
2016-11-29 20:33   ` [PATCH 4/4] md/raid5-cache: adjust the write position of the empty block and mark it as a checkpoint Song Liu
2016-11-29 22:31   ` Shaohua Li
2016-11-30  4:03     ` JackieLiu
2016-12-02 20:10       ` Shaohua Li
2016-12-05  3:58         ` JackieLiu
2016-12-06  1:00           ` Shaohua Li
2016-11-29 20:14 ` [PATCH 1/4] md/raid5-cache: remove unnecessary function parameters Song Liu

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=20161128081921.5641-4-liuyun01@kylinos.cn \
    --to=liuyun01@kylinos.cn \
    --cc=linux-raid@vger.kernel.org \
    --cc=liuzhengyuan@kylinos.cn \
    --cc=songliubraving@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.