DocumentUrlDB::del Only assert when children of dir actually exist
Review Request #128189 - Created June 14, 2016 and submitted
We can have cases when deleting a directory from DocumentUrlDB when we have some children stored under it which actually don't exist on the file system. This can happen when the dir is being removed from DB because it doesn't exist on the filesystem.
We do need to work on cleaning up the DB when we encounter such behaviour or even better figure out why it is happening and preventing it from happening.
Fixed crash on CoLa's laptop.
It's so strange that no matter what we still keep getting corrupted data.
If possible, it would be nice if you could save cola's baloo db and try to diagnose exactly what got corrupted. Or if it is small enough we can save it (after removing personal data) and use it as a test case.
Status: Closed (submitted)
Submitted with commit 1274870e43b879e24c2f76f69544868a021513d3 by Pinak Ahuja to branch master.
As there is no bugreport for this one to comment on, an idea how this can happen:
- A file is moved to a different directory
- The old directory is deleted
The docID is a concatenation of stat.device | stat.inode, thus won't change by moving the file.