dbcheck: don't move already deleted objects to LostAndFound
authorStefan Metzmacher <metze@samba.org>
Mon, 25 Feb 2019 14:35:22 +0000 (15:35 +0100)
committerKarolin Seeger <kseeger@samba.org>
Tue, 2 Apr 2019 09:10:52 +0000 (09:10 +0000)
commit0c2f7224e075538fc0fd70e4405cafc82f037909
tree3e070b130f6cfd0dc322169644ef1da0ba6d6b0b
parent95f5b9f246a46e5233108251a4122809aa0f1220
dbcheck: don't move already deleted objects to LostAndFound

This would typically happen when the garbage collection
removed a parent object before a child object (both with
the DISALLOW_MOVE_ON_DELETE bit set in systemFlags),
while dbcheck is running at the same time as the garbage collection.

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 6d50ee74920c39cdb18b427bfaaf200775bf2d73)
python/samba/dbchecker.py
selftest/knownfail.d/dbcheck-list-deleted
source4/selftest/provisions/release-4-5-0-pre1/expected-dbcheck-link-output-lost-deleted-user1.txt