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 <tst@1und1.de>
This commit is contained in:
Frank Liepold 2013-10-21 13:00:25 +02:00 committed by Thomas Schoebel-Theuer
parent 915f955333
commit 675e46d689

View File

@ -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++;
}