- Do not try to allocate more DB blocks in an inode block until it's "confirmed" and "locked" by the first write
- Do not recheck for new zero DB blocks on first write into an inode block - a CAS failure means someone else is already writing into it
- Throw new allocation blocks away regardless of whether the known_version is 0 on a CAS failure
- do not overwrite a block with older version if known version is newer
(read may start before update and end after update)
- invalidated block versions can't be remembered and trusted
- right boundary for split blocks is right_half when diving down, not key_lt
- restart update also when block is "invalidated", not just on version mismatch
- copy callback in listings to avoid closure destruction bugs too
- Prevent _split types of new blocks
- Stop updating new blocks only after the whole update, otherwise pointers
may become invalid
- Use recheck_none for updates initially
- Use UINT64_MAX as initial block version when postponing ops, otherwise the
check fails when the block is initially empty. This for example leads to
writing both leaf items & block pointers (which is incorrect) into the root
block when starting stress-test with --parallelism 32
- Fix -EINTR comparison
- track block versions correctly - per inode block (128kb) instead of tree block (4kb)
- prevent multiple parallel CAS writes of the same inode block
- add logging for EILSEQ which means invalid data in the tree
- fix get_block updated flag which was true for blocks already in cache and was leading to infinite loops on "unrelated block" errors
- apply changes to blocks in cache only after successful writes (using "virtual changes")
- do not replace cached block with an older version from disk
- recheck "unrelated blocks" (read/update collisions) until data stops changing
- track tree path correctly - do not treat split block as parent of its right half
- correctly move blocks when finding new empty place on disk
- restart updates from the beginning when one of blocks is changed by a parallel update
- fix delete using SET opcode and setting key to the empty value instead
- prevent changing the same key more than 1 time in parallel
- fix listing verification
- resume continue_updates in update_find (required because it uses continue_update itself)
- add allow_old_cached parameter to get()
Test / test_write_no_same (push) Successful in 23sDetails
Test / test_rebalance_verify_ec_imm (push) Successful in 5m2sDetails
Test / test_write_xor (push) Successful in 55sDetails
Test / test_rebalance_verify_ec (push) Successful in 6m22sDetails
Test / test_heal_pg_size_2 (push) Successful in 5m41sDetails
Test / test_heal_csum_32k_dmj (push) Successful in 5m59sDetails
Test / test_heal_csum_32k_dj (push) Successful in 7m19sDetails
Test / test_heal_csum_32k (push) Successful in 7m17sDetails
Test / test_heal_csum_4k_dmj (push) Successful in 7m14sDetails
Test / test_scrub (push) Successful in 1m12sDetails
Test / test_heal_ec (push) Successful in 9m2sDetails
Test / test_scrub_xor (push) Successful in 56sDetails
Test / test_scrub_zero_osd_2 (push) Successful in 1m8sDetails
Test / test_scrub_pg_size_6_pg_minsize_4_osd_count_6_ec (push) Successful in 2m1sDetails
Test / test_heal_csum_4k_dj (push) Successful in 4m45sDetails
Test / test_scrub_pg_size_3 (push) Successful in 2m31sDetails
Test / test_heal_csum_4k (push) Successful in 4m54sDetails
Test / test_scrub_ec (push) Successful in 46sDetails
- Do not use \r if output is not a terminal (should fix unexpected job output in proxmox)
- Fix rm/rm-data error return code, add --down-ok option to bypass the error
- Add EIO retry timeout and allow to disable these retries, rename up_wait_retry_interval to client_retry_interval
- Add ubuntu jammy build
- Wait for blockstore initialisation before starting OSD (prevent timeouts when init takes time)
- Fix a rare use-after-free in automatic sync after delete in blockstore
Vitaliy Filippov