There is only one key before
\x00, which is the empty key. This is why I typically recommend using the following command in
fdbcli to clear the whole database (note you must use double quotes
" instead of single quotes
clearrange "" \xff
When you run a clear range like this, you should see the sum of key value sizes drop quickly, but the disk space may take a while to recover. The empty key won’t hold 2 TB, though, so that wouldn’t explain your issue.
What happens if you run a range read on the main key space? It should return no keys:
getrange "" \xff
If that is empty, the next thing to check would be the
\xff key space. The most likely way of accumulating data there would be if you turned on backup or DR but didn’t have any agents to do the associated work.
An effective way to check this is to use the locality API to get shard boundaries. If you really have a lot of data somewhere, there should be a lot of shard boundaries that indicate where. In the Python bindings, for example, you would use:
fdb.locality.get_boundary_keys(db, b"", b"\xff\xff")
If that doesn’t turn up anything, or if turns up a bunch of shards which are in fact empty, then there may be something going wrong.