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 05:54:48 +0000 (15:54 +1000)
commit2fc6b6403707a292d134140fc0b9145b454992c5
treeb4297fe072c54b025b5e511274c215d1aa0358cc
parentca61eb776ab862bd269e45ee0f9f96e7e1e0e001
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>
client/ctdb_client.c