I can reproduce this bug in the following way:
- Create a datastore in local folder /srv/test1
- Delete that datastore
- Create a new datastore WHILE the previous one is still deleting, at folder /srv/test2
- When the job of the first datastore finished, BOTH gets deleted from the configuration.
Afterwards the chunks are still there, but the configuration is lost
- Create a datastore in local folder /srv/test1
- Delete that datastore
- Create a new datastore WHILE the previous one is still deleting, at folder /srv/test2
- When the job of the first datastore finished, BOTH gets deleted from the configuration.
Afterwards the chunks are still there, but the configuration is lost