From 675e46d689f7c9c1b9de1cac85b449fe90c978d3 Mon Sep 17 00:00:00 2001 From: Frank Liepold Date: Mon, 21 Oct 2013 13:00:25 +0200 Subject: [PATCH] light: report next logfile to be copyable in case of logfile sequence holes Up to now holes in the logfile sequence caused the copy process to stop after having fetched the last logfile before the hole. E.g. in emergency mode such holes are created intentionally on the primary side. After the situation has been cleaned up, the secondary must be able to fetch newly created logfiles. Signed-off-by: Thomas Schoebel-Theuer --- kernel/sy_old/mars_light.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sy_old/mars_light.c b/kernel/sy_old/mars_light.c index e4cb784f..0efa2299 100644 --- a/kernel/sy_old/mars_light.c +++ b/kernel/sy_old/mars_light.c @@ -1387,7 +1387,7 @@ int check_logfile(const char *peer, struct mars_dent *remote_dent, struct mars_d } // bookkeeping for serialization of logfile updates - if (remote_dent->d_serial == rot->copy_serial + 1) { + if (remote_dent->d_serial > rot->copy_serial) { rot->copy_next_is_available++; }