For some reasons when we delete a MergeTree Part in atomic way something may go wrong - and leave the `delete_tmp_*` folder or it's part on disk. This may lead to a disk space consumption over time.

It's suggested to delete this folders at least at server start-up. Current solution with `clearOldTemporaryDirectories()` doesn't work because this method is called periodically from a thread without any locks or advisory on folders - it may cause the race conditions.
update_error(it);
                continue;
            }
            if ((*it)->info.min_block > pos)
                update_error(it);
            if ((*it)->getState() != DataPartState::Active)
            {
                addPartContributionToColumnAndSecondaryIndexSizes(*it);
                addPartContributionToDataVolume(*it);
                modifyPartState(it, DataPartState::Active);
                restored_active_part = true;
            }
            pos = (*it)->info.max_block + 1;
            restored.push_back((*it)->name);
        }
        if (pos != part->info.max_block + 1)
            error = true;
        for (const String & name : restored)
        {
            LOG_INFO(log, "Activated part {}", name);
        }
        if (error)
        {
            LOG_ERROR(log, "The set of parts restored in place of {} looks incomplete. There might or might not be a data loss.{}", part->name, (error_parts.empty() ? "" : " Suspicious parts: " + error_parts));
        }
    }
    if (removed_active_part || restored_active_part)
        resetObjectColumnsFromActiveParts(lock);
}
void MergeTreeData::tryRemovePartImmediately(DataPartPtr && part)