The IntegrityService database should not be able to have files, which does not have a state on all pillars

In the staging environment at KB, the following SQL query on the IntegrityDB gave odd results:

SELECT DISTINCT(pillars) FROM (SELECT file_guid, COUNT(pillar_guid) AS pillars FROM fileinfo GROUP BY file_guid) as t1;

This query should only give 1 result (which must be equal to the number of pillars in the system).
But it oddly enough gave two answers, both 1 and 5 (the setup has 5 pillars).

This suggests an issue with the ingestion of file-ids into the database, since every file-id should be defined for every pillar.
Though there has been both power-failure and space issues on the machine, which might have caused this issue.