diff options
| author | Stefan Metzmacher <metze@samba.org> | 2019-02-28 18:22:18 +0100 |
|---|---|---|
| committer | Karolin Seeger <kseeger@samba.org> | 2019-03-28 12:19:13 +0000 |
| commit | 42c9e569e81238956b68f37bd445cc6c76268230 (patch) | |
| tree | f1cd29f7e09ca84db10ff1903ec635100fedcc34 /selftest | |
| parent | 08f7f33acb9a739505ed621d962913a4f212a190 (diff) | |
| download | samba-42c9e569e81238956b68f37bd445cc6c76268230.tar.gz | |
dbcheck: detect the change after deletion bug
Old versions of 'samba-tool dbcheck' could reanimate
deleted objects, when running at the same time as the
tombstone garbage collection.
When the (deleted) parent of a deleted object
(with the DISALLOW_MOVE_ON_DELETE bit in systemFlags),
is removed before the object itself, dbcheck moved
it in the LostAndFound[Config] subtree of the partition
as an originating change. That means that the object
will be in tombstone state again for 180 days on the local
DC. And other DCs fail to replicate the object as
it's already removed completely there and the replication
only gives the name and lastKnownParent attributes, because
all other attributes should already be known to the other DC.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=13816
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
(cherry picked from commit a1658b306d85452407388b91a745078c9c1f7dc7)
Diffstat (limited to 'selftest')
| -rw-r--r-- | selftest/knownfail.d/dbcheck-list-deleted | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/selftest/knownfail.d/dbcheck-list-deleted b/selftest/knownfail.d/dbcheck-list-deleted deleted file mode 100644 index 670e42b747c..00000000000 --- a/selftest/knownfail.d/dbcheck-list-deleted +++ /dev/null @@ -1,2 +0,0 @@ -^samba4.blackbox.dbcheck-links.release-4-5-0-pre1.lost_deleted_user2_clean -^samba4.blackbox.dbcheck-links.release-4-5-0-pre1.dbcheck_clean3 |