recoverd: Use TDB_INCOMPATIBLE_HASH when creating volatile databases
authorAmitay Isaacs <amitay@gmail.com>
Tue, 13 Aug 2013 04:02:46 +0000 (14:02 +1000)
committerAmitay Isaacs <amitay@gmail.com>
Wed, 14 Aug 2013 06:15:36 +0000 (16:15 +1000)
commitb0d147dbac28a4dd9a5d002ded3f0d0488009ebc
tree001833d73232100ae8399e2745185cb8f32bb4b5
parent1268ed6edbdee97f6757205bb10d1f285f6394c6
recoverd: Use TDB_INCOMPATIBLE_HASH when creating volatile databases

When creating missing databases either locally or remotely, recovery
master calls ctdb_ctrl_createdb().  Recovery master always passes 0
for tdb_flags.  For volatile databases, if TDB_INCOMPATIBLE_HASH is not
specified, then they will be attached without using jenkins hash causing
database corruption.

Signed-off-by: Amitay Isaacs <amitay@gmail.com>
(cherry picked from commit 2fc6b6403707a292d134140fc0b9145b454992c5)
client/ctdb_client.c