summaryrefslogtreecommitdiffstats
path: root/ctdb/lib/tdb/common
Commit message (Collapse)AuthorAgeFilesLines
* ctdb-build: Remove duplicate tdb libraryAmitay Isaacs2014-06-2015-7235/+0
| | | | | Signed-off-by: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org>
* tdb: Sync to tdb 1.2.11 from upstreamAmitay Isaacs2013-05-295-26/+406
| | | | (This used to be ctdb commit bb3a32ec055432afc7225c9fd7504fb187694bda)
* lib/tdb: Sync tdb from samba git treeAmitay Isaacs2012-04-1314-256/+568
| | | | | | Signed-off-by: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit 0f40ea2386892ae10b30beeded0e00edf4c019c3)
* change TDB to be valgrind niceRonnie Sahlberg2012-02-221-0/+2
| | | | (This used to be ctdb commit d306c3c9a53e012c412c96ab9743de6cd96826e0)
* tdb: expose transaction lock infrastructure for ctdbRusty Russell2011-01-181-0/+20
| | | | | | | | | tdb_traverse_read() grabs the transaction lock. This can cause ctdbd (which uses it) to block when it should not; expose mark and normal variants of this lock, so ctdbd's child (the recovery daemon) can acquire it and the ctdbd parent can mark it was held. (This used to be ctdb commit d09fa845bd848d04507853809acf42e0471b44bf)
* tdb: TDB_INCOMPATIBLE_HASH, to allow safe changing of default hash.Rusty Russell2010-10-073-4/+20
| | | | | | | | | | | | | | | | | | This flag to tdb_open/tdb_open_ex effects creation of a new database: 1) Uses the Jenkins lookup3 hash instead of the old gdbm hash if none is specified, 2) Places a non-zero field in header->rwlocks, so older versions of TDB will refuse to open it. This means that the caller (ie Samba) can set this flag to safely change the hash function. Versions of TDB from this one on will either use the correct hash or refuse to open (if a different hash is specified). Older TDB versions will see the nonzero rwlocks field and refuse to open it under any conditions. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit dd86b24ae5307fe09d4ae22b7070d747013a2b07)
* tdb: automatically identify Jenkins hash tdbsRusty Russell2010-10-071-14/+27
| | | | | | | | | | | | If the caller to tdb_open_ex() doesn't specify a hash, and tdb_old_hash doesn't match, try tdb_jenkins_hash. This was Metze's idea: it makes life simpler, especially with the upcoming TDB_INCOMPATIBLE_HASH flag. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 3f7ed2b46cb304d553d3f7bd34554d695b8ccc52)
* tdb: add Bob Jenkins lookup3 hash as helper hash.Rusty Russell2010-10-073-15/+382
| | | | | | | | | | | | This is a better hash than the default: shipping it with tdb makes it easy for callers to use it as the hash by passing it to tdb_open_ex(). This version taken from CCAN and modified, which took it from http://www.burtleburtle.net/bob/c/lookup3.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 58c9d90c758aa7c062d84ab97f62947190526356)
* lib/tdb: fix c++ build warning in tdb_header_hash().Günther Deschner2010-10-071-1/+1
| | | | | | Guenther (This used to be ctdb commit e34e639c214b010ff18140b769a8c9245c92006f)
* tdb: added TDB_NO_FSYNC env variableAndrew Tridgell2010-10-071-0/+4
| | | | | | this might help reduce test times and load on test machines (This used to be ctdb commit 5c4240c364c52073ca64fddf2aa2c1593db0093b)
* tdb: put example hashes into header, so we notice incorrect hash_fn.Rusty Russell2010-10-073-2/+65
| | | | | | | | | | | | This is Stefan Metzmacher <metze@samba.org>'s patch with minor changes: 1) Use the TDB_MAGIC constant so both hashes aren't of strings. 2) Check the hash in tdb_check (paranoia, really). 3) Additional check in the (unlikely!) case where both examples hash to 0. 4) Cosmetic changes to var names and complaint message. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 63c582c99128c3623e270e8425966cab7744fb2f)
* tdb: fix tdb_check() on other-endian tdbs.Rusty Russell2010-10-071-1/+1
| | | | | | | | We must not endian-convert the magic string, just the rest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 525390863ad39acea08ceb88531dc59d118fcad4)
* tdb: fix tdb_check() on read-only TDBs to actually work.Rusty Russell2010-10-071-5/+17
| | | | | | | | | | | | Commit bc1c82ea137 "Fix tdb_check() to work with read-only tdb databases." claimed to do this, but tdb_lockall_read() fails on read-only databases. Also make sure we can still do tdb_check() inside a transaction (weird, but we previously allowed it so don't break the API). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 2558eb250011893d09dbeaedaffeefa0e397142f)
* tdb: make check more robust against recovery failures.Rusty Russell2010-10-071-5/+36
| | | | | | | | | | | | | We can end up with dead areas when we die during transaction commit; tdb_check() fails on such a (valid) database. This is particularly noticable now we no longer truncate on recovery; if the recovery area was at the end of the file we used to remove it that way. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit b4162a95ff9ae28cda8d9c76c51c9480104517a7)
* tdb: workaround starvation problem in locking entire database.Rusty Russell2010-08-161-17/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (Imported from SAMBA 11ab43084b10cf53b530cdc3a6036c898b79ca38) We saw tdb_lockall() take 71 seconds under heavy load; this is because Linux (at least) doesn't prevent new small locks being obtained while we're waiting for a big log. The workaround is to do divide and conquer using non-blocking chainlocks: if we get down to a single chain we block. Using a simple test program where children did "hold lock for 100ms, sleep for 1 second" the time to do tdb_lockall() dropped signifiantly. There are ln(hashsize) locks taken in the contended case, but that's slow anyway. More analysis is given in my blog at http://rusty.ozlabs.org/?p=120 This may also help transactions, though in that case it's the initial read lock which uses this gradual locking routine; the update-to-write-lock code is separate and still tries to update in one go. Even though ABI doesn't change, minor version bumped so behavior change can be easily detected. CQ:S1018154 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 9ec0009443a0ac4187ce5212a5143689daa58a02)
* tdb: Fix tdb_check() to work with read-only tdb databases.Rusty Russell2010-08-161-3/+3
| | | | | | | | (Import from SAMBA bc1c82ea137e1bf6cb55139a666c56ebb2226b23) The function tdb_lockall() uses F_WRLCK internally, which doesn't work on a fd opened with O_RDONLY. Use tdb_lockall_read() instead. (This used to be ctdb commit a5db1122ec48d7e7384066848457c850c1a6cf3c)
* tdb: remove unused variable in tdb_new_database().Rusty Russell2010-08-161-1/+0
| | | | | | (Imported from SAMBA 2eab1d7fdcb54f9ec27431ca4858eb64cb1bd835) (This used to be ctdb commit 52a87e608d0406aee9df99f7ac3ce16e834b520b)
* tdb: fix short write logic in tdb_new_databaseRusty Russell2010-08-163-17/+17
| | | | | | | | | | | | | | Commit 207a213c/24fed55d purported to fix the problem of signals during tdb_new_database (which could cause a spurious short write, hence a failure). However, the code is wrong: newdb+written is not correct. Fix this by introducing a general tdb_write_all() and using it here and in the tracing code. Cc: Stefan Metzmacher <metze@samba.org> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 27ba0e5a6681063225df7244a85aa304c51c6948)
* tdb: update tdb ABI to use hide_symbols=TrueAndrew Tridgell2010-04-221-1/+1
| | | | | | | | | | | | | | | | | | We now use -fvisibilty=hidden to hide symbols from outside the tdb shared library. This also moved tdb_transaction_recover() into the tdb_private.h header, as it should never have been a public API. For that reason we are changing the version number. We're only doing a minor version increment as it is extremely unlikely that anyone was actually using tdb_transaction_recover() as its locking requirements were rather unusual. Pair-Programmed-With: Rusty Russell <rusty@samba.org> (Imported from commit 773a8afbba27a5e2e48577100f3ca9873b506615) (This used to be ctdb commit e174dc084f11db0eb239b643affef2c02c711b1c)
* tdb: Add a non-blocking version of tdb_transaction_startVolker Lendecke2010-04-224-7/+22
| | | | | | (Imported from commit 261c3b4f1beed820647061bacbee3acccbcbb089) (This used to be ctdb commit 87ced00d6d98be4a34719af58694e7c940b4dd68)
* tdb: Fix indentation in tdb_new_database()Volker Lendecke2010-04-221-1/+1
| | | | | | (Imported from commit 59315887a07033316edf91c0c57563eee5ea992d) (This used to be ctdb commit fa38f818c71c85918e673ff563bf7a91a0c4cc17)
* Fix some nonempty blank linesVolker Lendecke2010-04-2210-45/+44
| | | | | | (Imported from commit ea8e0d5d54b020c530e392c4edaeed43e20af303) (This used to be ctdb commit 7161cb1607bb105cd6f4f32df50f519314e77b3f)
* tdb: If tdb_parse_record does not find a record, return -1 instead of 0Volker Lendecke2010-04-221-1/+4
| | | | | | (Imported from commit fb98f60594b6cabc52d0f2f49eda08f793ba4748) (This used to be ctdb commit e90aba9967ea4a8ae7f6bdfc19666c47bd92951e)
* tdb: handle processes dying during transaction commit.Rusty Russell2010-04-223-0/+86
| | | | | | | | | | | | | | | | | | | | | | | | | | tdb transactions were designed to be robust against the machine powering off, but interestingly were never designed to handle the case where an administrator kill -9's a process during commit. Because recovery is only done on tdb_open, processes with the tdb already mapped will simply use it despite it being corrupt and needing recovery. The solution to this is to check for recovery every time we grab a data lock: we could have gained the lock because a process just died. This has no measurable cost: here is the time for tdbtorture -s 0 -n 1 -l 10000: Before: 2.75 2.50 2.81 3.19 2.91 2.53 2.72 2.50 2.78 2.77 = Avg 2.75 After: 2.81 2.57 3.42 2.49 3.02 2.49 2.84 2.48 2.80 2.43 = Avg 2.74 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit ec96ea690edbe3398d690b4a953d487ca1773f1c) (This used to be ctdb commit 4215c7025d2b29439c5acd19ce4e0fc4e67370b3)
* patch tdb-refactor-tdb_lock-and-tdb_lock_nonblock.patchRusty Russell2010-04-221-16/+13
| | | | | | (Imported from commit 1bf482b9ef9ec73dd7ee4387d7087aa3955503dd) (This used to be ctdb commit 52b0f19636565ef633e63d2726a1cc8c41dccedb)
* tdb: don't truncate tdb on recoveryRusty Russell2010-04-221-10/+0
| | | | | | | | | | | | The current recovery code truncates the tdb file on recovery. This is fine if recovery is only done on first open, but is a really bad idea as we move to allowing recovery on "live" databases. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 8c3fda4318adc71899bc41486d5616da3a91a688) (This used to be ctdb commit 65bc926d1a9cb3af18cae6b1462b832a5bcec561)
* tdb: remove lock opsRusty Russell2010-04-224-40/+22
| | | | | | | | | | | | | | | Now the transaction code uses the standard allrecord lock, that stops us from trying to grab any per-record locks anyway. We don't need to have special noop lock ops for transactions. This is a nice simplification: if you see brlock, you know it's really going to grab a lock. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 9f295eecffd92e55584fc36539cd85cd32c832de) (This used to be ctdb commit 6d7093cf51d0256245cc6bab24c9550ed3f1d8a5)
* tdb: rename tdb_release_extra_locks() to tdb_release_transaction_locks()Rusty Russell2010-04-223-13/+9
| | | | | | | | | | | | tdb_release_extra_locks() is too general: it carefully skips over the transaction lock, even though the only caller then drops it. Change this, and rename it to show it's clearly transaction-specific. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit a84222bbaf9ed2c7b9c61b8157b2e3c85f17fa32) (This used to be ctdb commit 803035716338170896fee15f15b17c32e7ee777e)
* tdb: cleanup: remove ltype argument from _tdb_transaction_cancel.Rusty Russell2010-04-221-17/+13
| | | | | | | | | | | | Now the transaction allrecord lock is the standard one, and thus is cleaned in tdb_release_extra_locks(), _tdb_transaction_cancel() doesn't need to know what type it is. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit dd1b508c63034452673dbfee9956f52a1b6c90a5) (This used to be ctdb commit 74874ffb2c81e098c1d7935b37557c2151382ca6)
* tdb: tdb_allrecord_lock/tdb_allrecord_unlock/tdb_allrecord_upgradeRusty Russell2010-04-223-29/+62
| | | | | | | | | | | | | | | | | | | | | Centralize locking of all chains of the tdb; rename _tdb_lockall to tdb_allrecord_lock and _tdb_unlockall to tdb_allrecord_unlock, and tdb_brlock_upgrade to tdb_allrecord_upgrade. Then we use this in the transaction code. Unfortunately, if the transaction code records that it has grabbed the allrecord lock read-only, write locks will fail, so we treat this upgradable lock as a write lock, and mark it as upgradable using the otherwise-unused offset field. One subtlety: now the transaction code is using the allrecord_lock, the tdb_release_extra_locks() function drops it for us, so we no longer need to do it manually in _tdb_transaction_cancel. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit fca1621965c547e2d076eca2a2599e9629f91266) (This used to be ctdb commit d7fdb38ac05b5f2af9eb485e98673280835273dd)
* tdb: suppress record write locks when allrecord lock is taken.Rusty Russell2010-04-221-0/+9
| | | | | | | | | | | | | | | | | | | Records themselves get (read) locked by the traversal code against delete. Interestingly, this locking isn't done when the allrecord lock has been taken, though the allrecord lock until recently didn't cover the actual records (it now goes to end of file). The write record lock, grabbed by the delete code, is not suppressed by the allrecord lock. This is now bad: it causes us to punch a hole in the allrecord lock when we release the write record lock. Make this consistent: *no* record locks of any kind when the allrecord lock is taken. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit caaf5c6baa1a4f340c1f38edd99b3a8b56621b8b) (This used to be ctdb commit 7a99cdf5d0a91764a750c1a264e90e5b66f910a1)
* tdb: cleanup: always grab allrecord lock to infinity.Rusty Russell2010-04-221-7/+3
| | | | | | | | | | | | | | We were previously inconsistent with our "global" lock: the transaction code grabbed it from FREELIST_TOP to end of file, and the rest of the code grabbed it from FREELIST_TOP to end of the hash chains. Change it to always grab to end of file for simplicity and so we can merge the two. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 9341f230f8968b4b18e451d15dda5ccbe7787768) (This used to be ctdb commit 46f2c33357c999c31a8064c159c6162269c28d9d)
* tdb: remove num_locksRusty Russell2010-04-222-11/+2
| | | | | | | | | | | | | | This was redundant before this patch series: it mirrored num_lockrecs exactly. It still does. Also, skip useless branch when locks == 1: unconditional assignment is cheaper anyway. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 1ab8776247f89b143b6e58f4b038ab4bcea20d3a) (This used to be ctdb commit 587ac01ce836286aab54bfcb7a693a0170c7ebd3)
* tdb: use tdb_nest_lock() for seqnum lock.Rusty Russell2010-04-221-3/+3
| | | | | | | | | | | This is pure overhead, but it centralizes the locking. Realloc (esp. as most implementations are lazy) is fast compared to the fnctl anyway. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit d48c3e4982a38fb6b568ed3903e55e07a0fe5ca6) (This used to be ctdb commit 2e8512403525c14c9b776ce28891d09c17ada91d)
* tdb: use tdb_nest_lock() for active lock.Rusty Russell2010-04-222-5/+18
| | | | | | | | | | | | | Use our newly-generic nested lock tracking for the active lock. Note that the tdb_have_extra_locks() and tdb_release_extra_locks() functions have to skip over this lock now it is tracked. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 4738d474c412cc59d26fcea64007e99094e8b675) (This used to be ctdb commit 0a44584963232b0b1c62e30c9bede0439e68ef7d)
* tdb: use tdb_nest_lock() for open lock.Rusty Russell2010-04-223-15/+10
| | | | | | | | | | | | | | | This never nests, so it's overkill, but it centralizes the locking into lock.c and removes the ugly flag in the transaction code to track whether we have the lock or not. Note that we have a temporary hack so this places a real lock, despite the fact that we are in a transaction. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 9136818df30c7179e1cffa18201cdfc990ebd7b7) (This used to be ctdb commit 6812d81907793299e874f121174d885f6500f374)
* tdb: use tdb_nest_lock() for transaction lock.Rusty Russell2010-04-222-32/+23
| | | | | | | | | | | | | | Rather than a boutique lock and a separate nest count, use our newly-generic nested lock tracking for the transaction lock. Note that the tdb_have_extra_locks() and tdb_release_extra_locks() functions have to skip over this lock now it is tracked. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit e8fa70a321d489b454b07bd65e9b0d95084168de) (This used to be ctdb commit 4ca1b96a70048b2eaa0d12fb5f0fdb54ec396aa3)
* tdb: cleanup: find_nestlock() helper.Rusty Russell2010-04-221-28/+23
| | | | | | | | | | | Factor out two loops which find locks; we are going to introduce a couple more so a helper makes sense. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit ce41411c84760684ce539b6a302a0623a6a78a72) (This used to be ctdb commit cfb154dd0f189f37b937e90144c2eb9e66a26420)
* tdb: cleanup: tdb_release_extra_locks() helperRusty Russell2010-04-223-17/+22
| | | | | | | | | | | Move locking intelligence back into lock.c, rather than open-coding the lock release in transaction.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit db270734d8b4208e00ce9de5af1af7ee11823f6d) (This used to be ctdb commit d2dd720b51c4032e5d77d30212da8117d3f119df)
* tdb: cleanup: tdb_have_extra_locks() helperRusty Russell2010-04-224-5/+17
| | | | | | | | | | | | | In many places we check whether locks are held: add a helper to do this. The _tdb_lockall() case has already checked for the allrecord lock, so the extra work done by tdb_have_extra_locks() is merely redundant. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit fba42f1fb4f81b8913cce5a23ca5350ba45f40e1) (This used to be ctdb commit dda3587dfee598f387c2e696f3645486fac65052)
* tdb: don't suppress the transaction lock because of the allrecord lock.Rusty Russell2010-04-221-6/+0
| | | | | | | | | | | | | | | | | | | | | | tdb_transaction_lock() and tdb_transaction_unlock() do nothing if we hold the allrecord lock. However, the two locks don't overlap, so this is wrong. This simplification makes the transaction lock a straight-forward nested lock. There are two callers for these functions: 1) The transaction code, which already makes sure the allrecord_lock isn't held. 2) The traverse code, which wants to stop transactions whether it has the allrecord lock or not. There have been deadlocks here before, however this should not bring them back (I hope!) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit b754f61d235bdc3e410b60014d6be4072645e16f) (This used to be ctdb commit 495f3554259b9dbf9ee673c4fe420d98e50e4901)
* tdb: cleanup: tdb_nest_lock/tdb_nest_unlockRusty Russell2010-04-223-45/+67
| | | | | | | | | | | | | | | | | | | | | | Because fcntl locks don't nest, we track them in the tdb->lockrecs array and only place/release them when the count goes to 1/0. We only do this for record locks, so we simply place the list number (or -1 for the free list) in the structure. To generalize this: 1) Put the offset rather than list number in struct tdb_lock_type. 2) Rename _tdb_lock() to tdb_nest_lock, make it non-static and move the allrecord check out to the callers (except the mark case which doesn't care). 3) Rename _tdb_unlock() to tdb_nest_unlock(), make it non-static and move the allrecord out to the callers (except mark again). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 5d9de604d92d227899e9b861c6beafb2e4fa61e0) (This used to be ctdb commit 28576ddbd9bf91049db8a4f9e9e7856ac5b8f48a)
* tdb: cleanup: rename global_lock to allrecord_lock.Rusty Russell2010-04-225-29/+29
| | | | | | | | | | | | | The word global is overloaded in tdb. The global_lock inside struct tdb_context is used to indicate we hold a lock across all the chains. Rename it to allrecord_lock. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit e9114a758538d460d4f9deae5ce631bf44b1eff8) (This used to be ctdb commit a912657fb50a78b9b328c4564281fb9f7f1b3766)
* tdb: cleanup: rename GLOBAL_LOCK to OPEN_LOCK.Rusty Russell2010-04-223-17/+17
| | | | | | | | | | | | | | The word global is overloaded in tdb. The GLOBAL_LOCK offset is used at open time to serialize initialization (and by the transaction code to block open). Rename it to OPEN_LOCK. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 7ab422d6fbd4f8be02838089a41f872d538ee7a7) (This used to be ctdb commit a4f83910a485cf56f9b3df1dcf2ad36ebec57473)
* tdb: make _tdb_transaction_cancel static.Rusty Russell2010-04-222-2/+1
| | | | | | | | | | | Now tdb_open() calls tdb_transaction_cancel() instead of _tdb_transaction_cancel, we can make it static. Signed-off-by: Rusty Russell<rusty@rustcorp.com.au> (Imported from commit a6e0ef87d25734760fe77b87a9fd11db56760955) (This used to be ctdb commit d728a7f65bcd5f1aedbee41d6db5c35f10cb417e)
* tdb: cleanup: split brlock and brunlock methods.Rusty Russell2010-04-227-117/+235
| | | | | | | | | | | | | | | | | | | | | This is taken from the CCAN code base: rather than using tdb_brlock for locking and unlocking, we split it into brlock and brunlock functions. For extra debugging information, brunlock says what kind of lock it is unlocking (even though fnctl locks don't need this). This requires an extra argument to tdb_transaction_unlock() so we know whether the lock was upgraded to a write lock or not. We also use a "flags" argument tdb_brlock: 1) TDB_LOCK_NOWAIT replaces lck_type = F_SETLK (vs F_SETLKW). 2) TDB_LOCK_MARK_ONLY replaces setting TDB_MARK_LOCK bit in ltype. 3) TDB_LOCK_PROBE replaces the "probe" argument. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit 452b4a5a6efeecfb5c83475f1375ddc25bcddfbe) (This used to be ctdb commit 7b5fdc9c588237c83a1e70e5437e2e5510055b92)
* Spelling fixes for tdb.Brad Hards2010-04-222-2/+2
| | | | | | | | Signed-off-by: Matthias Dieter Wallnöfer <mwallnoefer@yahoo.de> (Imported from commit 09e756b1d651caef203a4b7e02234f6dea374b08) (This used to be ctdb commit b0dff4ed35ab2423b8fcc801cdaaebaa0d7654bb)
* tdb: use fdatasync() instead of fsync() in transactionsAndrew Tridgell2010-04-221-1/+1
| | | | | | | | This might help on some filesystems (Imported from commit 1373e748aa53fbd3afe4d2377208257d42628d86) (This used to be ctdb commit e9ee4aaeb471a7f5ba4c97d3f76f406c1fe9b92f)
* tdb: Apply some const, just for clarityVolker Lendecke2010-04-221-1/+1
| | | | | | (Imported from commit 6824c6f46ba7c15e8af91d5aa8b21a946b63107b) (This used to be ctdb commit 8b0a8a96edf8611257e58ea81ed872dc03ca5da6)
* tdb: fix recovery reuse after crashRusty Russell2010-04-221-4/+10
| | | | | | | | | | | | | | | | | | | If a process (or the machine) dies after just after writing the recovery head (pointing at the end of file), the recovery record will filled with 0x42. This will not invoke a recovery on open, since rec.magic != TDB_RECOVERY_MAGIC. Unfortunately, the first transaction commit will happily reuse that area: tdb_recovery_allocate() doesn't check the magic. The recovery record has length 0x42424242, and it writes that back into the now-valid-looking transaction header) for the next comer (which happens to be tdb_wipe_all in my tests). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit b37b452cb8c1f56b37b04abe7bffdede371ca361) (This used to be ctdb commit 8c8782ecbb347e026f67d82a39555c0e43b1e9f8)
generated by cgit (git 2.34.1) at 2025-09-26 04:41:30 +0000