From 651dd6d25e307f08ab63080b0afdba4762ad2bb5 Mon Sep 17 00:00:00 2001 From: Andrew Deason Date: Wed, 24 Nov 2010 10:03:19 -0500 Subject: [PATCH] ubik: Log a message when we replay the trans log It can be helpful to know that an interrupted transaction was replayed on startup, and this should be rare. So log a message when that happens, indicating what db version we replayed to. Reviewed-on: http://gerrit.openafs.org/3385 Tested-by: BuildBot Reviewed-by: Derrick Brashear (cherry picked from commit d29550a438a60dd918938f484c7b75e25478abd9) Change-Id: Ic3c8ec68febae8b61b6d04ef4d063178dffe8d0e Reviewed-on: http://gerrit.openafs.org/5753 Reviewed-by: Derrick Brashear Tested-by: Derrick Brashear --- src/ubik/recovery.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/ubik/recovery.c b/src/ubik/recovery.c index 45e9b018d..3ad7b9853 100644 --- a/src/ubik/recovery.c +++ b/src/ubik/recovery.c @@ -288,6 +288,9 @@ ReplayLog(struct ubik_dbase *adbase) code = (*adbase->setlabel) (adbase, 0, &version); if (code) return code; + ubik_print("Successfully replayed log for interrupted " + "transaction; db version is now %ld.%ld\n", + (long) version.epoch, (long) version.counter); logIsGood = 1; break; /* all done now */ } else if (opcode == LOGTRUNCATE) { -- 2.39.5