(In reply to Peter Gervai from comment #12)
Thanks for providing that directory!
Created attachment 9054155 [details]
It's not related to the name of the directory, in fact renamed to "buggy" and it still produced the error, had to move away from .../storage/ altogether.
Attaching, I believe there's no private info in them.
So, renaming it to "buggy" is expected to break your storage because such file name is not allowed to exist in that directory. And just make sure there is nothing unexpected, did you mean you move it from ".../stroage/default/"? I expected this should live under either "default", "temporary", or "permanent" directory.
I cannot reproduce the issue by adding to the current storage test for upgrading from 2_1 to 2_2 . (The test will pass).
Running with that with a debug build which has been upgraded to 2_2 already would still successfully initialize the storage. However, I got the following message:
[Parent 7814, QuotaManager IO] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80630001: file /Users/tomtung/Work/mozilla-central/storage/mozStorageConnection.cpp, line 698
[Parent 7814, QuotaManager IO] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80630001: file /Users/tomtung/Work/mozilla-central/storage/mozStorageService.cpp, line 671
[Parent 7814, QuotaManager IO] WARNING: Received NS_ERROR_STORAGE_BUSY when attempting to open database '3870112724rsegmnoittet-es.sqlite', retrying for up to 10 seconds: file /Users/tomtung/Work/mozilla-central/dom/indexedDB/ActorsParent.cpp, line 4081