From 3c244706a59ca0a0fc0c551dd260e58065b93822 Mon Sep 17 00:00:00 2001 From: Thomas Schoebel-Theuer Date: Wed, 25 May 2016 06:56:10 +0200 Subject: [PATCH] main: fix replay_code report in primary mode After a primary --force, the error couldn't go away in case of a defective logfile. Months later, sysadmins were needlessly alarmed when looking at the primary. --- kernel/sy_old/mars_main.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kernel/sy_old/mars_main.c b/kernel/sy_old/mars_main.c index 41eefd1f..b4f5741d 100644 --- a/kernel/sy_old/mars_main.c +++ b/kernel/sy_old/mars_main.c @@ -3769,8 +3769,10 @@ int make_log_finalize(struct mars_global *global, struct mars_dent *dent) } else if (rot->replay_code >= 0) { rot->replay_code = trans_brick->replay_code; } - __show_actual(parent->d_path, "replay-code", rot->replay_code); + } else { + rot->replay_code = 0; } + __show_actual(parent->d_path, "replay-code", rot->replay_code); /* Stopping is also possible in case of errors */