summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Enhance the "ctdb restoredb" command so you can restore a backup into a ↵Ronnie Sahlberg2010-05-201-5/+11
| | | | | | | | | | | | different database. (This used to be ctdb commit c692b09851fce85b61c8c654faafb49db8cb601b)
* | Merge commit 'obnox/master-rebase'Ronnie sahlberg2010-05-112-2/+7
|\ \ | |/ |/| | | (This used to be ctdb commit 3f0346dc758d3b05ccb86785e7c8a2d5679ff68c)
| * functions: when checking for a directory also check whether it can be accessed.Michael Adam2010-05-111-1/+1
| | | | | | | | | | | | | | | | Thanks to "waKKu" on irc for this improvement. Michael (This used to be ctdb commit 81e1483dd0ce2cd091721e456c0c194cc58442f3)
| * tests:ctdb_bench: make send_start_messages() static - eliminates compile warningMichael Adam2010-05-111-1/+1
| | | | | | | | | | | | Michael (This used to be ctdb commit e1a16c23d7dbf011ad220572f1bf081331efa8f8)
| * tests: eliminate a floating point exception by requiring -n option to ctdb_benchMichael Adam2010-05-111-0/+5
| | | | | | | | | | | | Michael (This used to be ctdb commit 07823e1fe75c588b75f4e42c80b0a7bc974238f7)
* | Add the number of performed recoveries to the "ctdb statistics" output.Ronnie Sahlberg2010-05-113-0/+3
| | | | | | | | (This used to be ctdb commit fa045733cb81412f0d02ab52d74eabc7efca8b3d)
* | ctdb: use full range of IDRRusty Russell2010-05-112-7/+4
|/ | | | | | | | | | | | | This resolves a problem with huge numbers of requests which could overflow 16 bits. Fortunately, the IDR should scale reasonably well, so we can simply hold all the requests. Although noone checks for failure, I added a constant for that. BZ: 60540 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 72efc4122e37798227c3420a65ed1f706ca9ebe7)
* when performing a recovery,Ronnie Sahlberg2010-05-061-0/+40
| | | | | | ensure that all nodes use the same reclock file setting as the recovery master (This used to be ctdb commit 26793ad42b77c2328a00ac9a12bca813c7425245)
* Add a new eventscript 62.cnfs to integrate better with gpfs/cnfsRonnie Sahlberg2010-05-043-0/+131
| | | | (This used to be ctdb commit 4a679422dc231aa98605b9cc322e4ab442f7bde4)
* Merge commit 'rusty/signal-fix'Ronnie sahlberg2010-05-033-53/+59
|\ | | | | | | (This used to be ctdb commit 221a9bb41c3a7af0cc65cda78365010893ca1430)
| * eventscript: simplify script timeout handlingRusty Russell2010-04-081-26/+4
| | | | | | | | | | | | | | | | | | | | Now the script child signal handler doesn't do anything, we can unify the "timeout" and "abort" cases introduced in 9dd25cb751919799. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 439f049c7024d69aa4b87dc811e1772981ad29cb)
| * eventscript: wait for debugging dump before killing timedout scriptRusty Russell2010-04-081-5/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Fairly simple: prevent the destructor from killing the script, and do it explicitly from the debugging child. We can remove the extra "already dead" test, since this will be detected in the destructor anyway. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit f8aa83788e3cc10ab7655a90d7b7b17ddbe48685)
| * eventscript: don't do debugging system() from inside signal handlerRusty Russell2010-04-083-22/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the case of a timeout, we dump a log of what's happening to a file in /tmp. We do it from the signal handler, which is an unreliable hack (BZ58365). Instead, create another (lower-priority) child to do the dump, then kill the timedout script. Note that this doesn't quite work as intended (the dump is often run after the script has been killed), so the next patch resolves this. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 7ee5ecc8d53e78e2dec21197b74a74cc4ae1834c)
| * eventscript: fix case where we fail to create child for some reasonRusty Russell2010-04-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Initialize the child pid to 0 so destructor doesn't try to kill it: server/eventscript.c:565 Sending SIGTERM to child pid:139742328 Failed to kill child process for eventscript, errno No such process(3) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit fcc63e04beb427c1f48deae6d3d98c78a2a67949)
* | Dont check ip assignment across the cluster while ip-verificationRonnie Sahlberg2010-05-031-3/+5
| | | | | | | | | | | | checks are disabled (This used to be ctdb commit 189f4a5af1053271b0834522e35c336df959aa03)
* | The recent change to the recovery daemon to keep track of andRonnie Sahlberg2010-05-035-0/+64
| | | | | | | | | | | | | | | | | | | | | | | | verify that all nodes agree on the most recent ip address assignments broke "ctdb moveip ..." since that call would never trigger a full takeover run and thus would immediately trigger an inconsistency. Add a new message to the recovery daemon where we can tell the recovery daemon to update its assignments. BZ62782 (This used to be ctdb commit e7069082e5f0380dcddee247db8754218ce18cab)
* | Make create_merged_ip_list() a static function sinceRonnie Sahlberg2010-05-031-1/+1
| | | | | | | | | | | | it is not called from outside of ctdb_takeover.c (This used to be ctdb commit 880896a27adfdd5173b2810b6b2f3889802046f0)
* | In the log message when we have found an inconsistent ip address allocation,Ronnie Sahlberg2010-05-031-1/+1
|/ | | | | | add extra log information about what the inconsistency is. (This used to be ctdb commit d2e4a9912c4bd13eb4f12681adebe7e59a6d1fb2)
* If the admin makes a configuration mistake and configures NATGW to use theRonnie Sahlberg2010-04-281-0/+9
| | | | | | | | | | | same ip address as a normal public-address, check for this in the natgw script and warn the user. Also prevent ctdb from starting up since this configuration will not work. BZ60933 (This used to be ctdb commit 480af69b63b9162c85d8e04461ca9e4a083c04a4)
* Merge commit 'rusty/tdb-update'Ronnie sahlberg2010-04-2322-520/+883
|\ | | | | | | (This used to be ctdb commit 35d9ac7d162f99795ac3146fcd464e9d2e45feaa)
| * 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)
| * 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)
generated by cgit (git 2.34.1) at 2025-10-02 08:28:33 +0000