summaryrefslogtreecommitdiffstats
path: root/ctdb/lib/tdb
Commit message (Collapse)AuthorAgeFilesLines
* ctdb:build: fix building with external libtdbMichael Adam2014-06-161-7/+7
| | | | | Signed-off-by: Michael Adam <obnox@samba.org> Reviewed-by: Jelmer Vernooij <jelmer@samba.org>
* samba:python - Py_RETURN_NONE remove compatibility code for releases < 2.4Matthias Dieter Wallnöfer2014-01-091-4/+0
| | | | | | | | | http://www.python.org/doc//current/c-api/none.html Reviewed-By: Jelmer Vernooij <jelmer@samba.org> Autobuild-User(master): Matthias Dieter Wallnöfer <mdw@samba.org> Autobuild-Date(master): Thu Jan 9 16:27:47 CET 2014 on sn-devel-104
* tdb: Sync to tdb 1.2.11 from upstreamAmitay Isaacs2013-05-2965-47/+6474
| | | | (This used to be ctdb commit bb3a32ec055432afc7225c9fd7504fb187694bda)
* lib/tdb: Sync tdb from samba git treeAmitay Isaacs2012-04-1324-423/+1547
| | | | | | Signed-off-by: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit 0f40ea2386892ae10b30beeded0e00edf4c019c3)
* lib/tdb: Remove the files required to build tdb as a libraryAmitay Isaacs2012-04-1320-4435/+0
| | | | | | | | | Since tdb library will never be built from ctdb sources, we don't need the build related files. Signed-off-by: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit a7aace3d165e6cb7d63950107e584edaee12a357)
* build: Use system tdb library if availableAmitay Isaacs2012-03-301-21/+45
| | | | | | Signed-off-by: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit 10ab88a5c822ac403a70a9cd1a6c81020eb91d08)
* 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-182-0/+24
| | | | | | | | | 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)
* pytdb: Add __version__ attribute.Jelmer Vernooij2010-10-072-0/+8
| | | | (This used to be ctdb commit 2b81314eb94d31f4efadd2a3dcf2f6e176338d3f)
* pytdb: Include Python.h first to prevent warning.Jelmer Vernooij2010-10-071-1/+1
| | | | (This used to be ctdb commit 247dacde0d0de1358cc2c27d08914be605272023)
* pytdb: Check errors after PyObject_New() callsKirill Smelkov2010-10-071-0/+7
| | | | | | | | | | The call could fail with e.g. MemoryError, and we'll dereference NULL pointer without checking. Signed-off-by: Kirill Smelkov <kirr@landau.phys.spbu.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit 09369aa86e233a58ed131fa5b7584b6c86527d40)
* pytdb: Add support for tdb_repack()Kirill Smelkov2010-10-072-0/+15
| | | | | | | | Cc: 597386@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@landau.phys.spbu.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit ce84abcc6be31554da73920280e6bfc5b63b1464)
* pytdb: Add TDB_INCOMPATIBLE_HASH open flagKirill Smelkov2010-10-071-0/+1
| | | | | | | | | | | | | In 2dcf76 Rusty added TDB_INCOMPATIBLE_HASH open flag which selects Jenkins lookup3 hash for new databases. Expose this flag to python users too. Cc: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit 07880810941850e81442b888cd70d810d3f80fc3)
* tdb: fix non-WAF build, commit 1.2.6 ABI file.Rusty Russell2010-10-072-1/+62
| | | | | | | | Sorry Jeremy. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 7db9838cb5af0d334efbbcb96bfa51d19b35941a)
* tdb: TDB_INCOMPATIBLE_HASH, to allow safe changing of default hash.Rusty Russell2010-10-075-5/+22
| | | | | | | | | | | | | | | | | | 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-075-16/+384
| | | | | | | | | | | | 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)
* tdb: add restoreVolker Lendecke2010-10-073-1/+239
| | | | | | Based on an idea by Simon McVittie, largely rewritten (This used to be ctdb commit 7cda5507f90d7598d745a1acfc66c2afa73cd4b5)
* 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)
* pytdb: Make filename argument optional.Jelmer Vernooij2010-10-072-13/+15
| | | | (This used to be ctdb commit 3cc73c51caff51e0cba688aefd6f37e632c0e8d4)
* pytdb: Add support for tdb_freelist_size()Kirill Smelkov2010-10-072-0/+9
| | | | | | | | Cc: 597386@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@landau.phys.spbu.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit dcdd83e6d6786f0857acdf9aa04bca74a7ccf14d)
* pytdb: Add support for tdb_transaction_prepare_commit()Kirill Smelkov2010-10-072-0/+18
| | | | | | | | Cc: 597386@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@landau.phys.spbu.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit fd16bcc1434841d84fdf78f80163c97c0b52b3fe)
* pytdb: Add support for tdb_enable_seqnum, tdb_get_seqnum and ↵Kirill Smelkov2010-10-072-0/+30
| | | | | | | | | | tdb_increment_seqnum_nonblock Cc: 597386@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@landau.phys.spbu.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit 1778fd02eec6e64737167c46173c0c76c85cc4d9)
* pytdb: Update open flags to match those for tdb_open() in tdb.hKirill Smelkov2010-10-071-0/+6
| | | | | | | | | | | Namely TDB_NOSYNC, TDB_SEQNUM, TDB_VOLATILE, TDB_ALLOW_NESTING and TDB_DISALLOW_NESTING were missing. Cc: 597386@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit d0c28ff1fedd27a99a7550fcc74e18cb1f536986)
* pytdb: Fix repr segfault for internal dbKirill Smelkov2010-10-072-1/+11
| | | | | | | | | | | | | | | | | The problem was tdb->name is NULL for TDB_INTERNAL databases, and so it was crashing ... #0 0xb76944f3 in strlen () from /lib/i686/cmov/libc.so.6 #1 0x0809862b in PyString_FromFormatV (format=0xb72b6a26 "Tdb('%s')", vargs=0xbfc26a94 "") at ../Objects/stringobject.c:211 #2 0x08098888 in PyString_FromFormat (format=0xb72b6a26 "Tdb('%s')") at ../Objects/stringobject.c:358 #3 0xb72b65f2 in tdb_object_repr (self=0xb759e060) at ./pytdb.c:439 Cc: 597089@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit 3ff413baf04ce28eb54a80141250ae1284b2a521)
* pytdb: Add support for tdb_add_flags() & tdb_remove_flags()Kirill Smelkov2010-10-072-0/+27
| | | | | | | | | | | Note, unlike tdb_open where flags is `int', tdb_{add,remove}_flags want flags as `unsigned', so instead of "i" I used "I" in PyArg_ParseTuple. Cc: 597386@bugs.debian.org Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru> Signed-off-by: Jelmer Vernooij <jelmer@samba.org> (This used to be ctdb commit 7389f8a8a634c2fe0f068831326d92e6bfa0d046)
* 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: increment version to 1.2.4Rusty Russell2010-10-071-1/+1
| | | | (This used to be ctdb commit f1c06608245ec34493c330d891e04c250ad64b20)
* 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-162-18/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (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: define _PUBLIC_ so we can compile tdb.Rusty Russell2010-04-221-0/+5
| | | | | | | | | | | The Samba tree defines _PUBLIC_ (and _PRIVATE_) for libraries to control visibility. The last commit absorbed this from their tdb, but we need to #define to stub it out since ctdb doesn't use it (and doesn't need to: we only use tdb internally). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 54bee0ec670724c337b882e7dda3e999ffa80691)
* tdb: update tdb ABI to use hide_symbols=TrueAndrew Tridgell2010-04-224-77/+65
| | | | | | | | | | | | | | | | | | 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)
* subunit: Support formatting compatible with upstream subunit, for consistency.Jelmer Vernooij2010-04-221-1/+1
| | | | | | | | | | Upstream subunit makes a ":" after commands optional, so I've fixed any places where we might trigger commands accidently. I've filed a bug about this in subunit. (Imported from commit 7da94cc4a664521be279b019e9f32121cd410193) (This used to be ctdb commit f1242d9cba676d1d393375bea42613192c70662e)
* tdb: update exports and signatures filesSimo Sorce2010-04-222-0/+2
| | | | | | (Imported from commit c1f6f61f620e865516d1856c9d937b5326a29046) (This used to be ctdb commit e61ff181085b35cb4aba933350bfe4f64471b359)
* tdb: Add a non-blocking version of tdb_transaction_startVolker Lendecke2010-04-226-8/+24
| | | | | | (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)
* python: use '#!/usr/bin/env python' to cope with varying install locationsAndrew Tridgell2010-04-222-2/+2
| | | | | | | | this should be much more portable (Imported from commit 088096d1bad51428a2e2d487214995d4fdfc7ccc) (This used to be ctdb commit 7f1330adc690360a4a8ce85352df0908a93684a5)
* tdb: Fix bug 7248, avoid the nanosleep dependencyVolker Lendecke2010-04-221-4/+4
| | | | | | (Imported from commit e2c7e5c4f72565fe49265d5b036531926ea1ac92) (This used to be ctdb commit 3318c74386e202b77ba7e29b4c3e0ce4d88fcd5b)
* tdb: If tdb_parse_record does not find a record, return -1 instead of 0Volker Lendecke2010-04-222-1/+23
| | | | | | (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: add -k option to tdbtortureRusty Russell2010-04-221-57/+142
| | | | | | | | | | | | | | | | | To test the case of death of a process during transaction commit, add a -k (kill random) option to tdbtorture. The easiest way to do this is to make every worker a child (unless there's only one child), which is why this patch is bigger than you might expect. Using -k without -t (always transactions) you expect corruption, though it doesn't happen every time. With -t, we currently get corruption but the next patch fixes that. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (Imported from commit ececeffd85db1b27c07cdf91a921fd203006daf6) (This used to be ctdb commit e5af0ce79c74f11daae2a8514e398c40535e2e67)
* 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)
generated by cgit (git 2.34.1) at 2025-09-02 02:54:57 +0000