Automatically clean up incomplete mirror state data

[Stefano Rivera]

18:55 < lifeless> its just that until the initial metadata is written, you could get a state where lmirror thinks you have a mirror set
18:56 < lifeless> but the mirrorset is actually fully defined
18:56 < lifeless> like - it has to mkdir .lmirror/sets/<name>, and write to .lmirror/sets/<name>/set.conf
18:57 < lifeless> if you interrupt it between those two, its in a bit of a limbo
18:57 < lifeless> File a bug - we can definitely write up what needs to be manually removed to clean up something that is interrupted too early
18:57 < tumbleweed> one probably wants to detect such broken sets then
18:58 < lifeless> that too - two bugs! :)

[Robert Collins (lifeless)]

We can definitely detect and warn, detecting and cleaning up might be too much. Perhaps detect and move-out-of-the-way, that way the user can undo the recovery if in fact it was misdiagnosed (e.g. due to them not mounting a volume)