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)
committerAndrew Bartlett <abartlet@samba.org>
Thu, 14 Mar 2019 02:12:20 +0000 (02:12 +0000)
commit6d50ee74920c39cdb18b427bfaaf200775bf2d73
tree310d06f060ff06d2a8cdc60e5e7c6a42b9d6e8d4
parent9afcd5331ce567bd80d35175f8e4e21c506e9347
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>
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