FileAPI: Run database recovery on IOError.

webkit/fileapi/file_system_directory_database.cc

Index: webkit/fileapi/file_system_directory_database.cc
diff --git a/webkit/fileapi/file_system_directory_database.cc b/webkit/fileapi/file_system_directory_database.cc
index 8618b98d308d0e698dd18fd01e0cbc459cd3559d..bbdc857fc4d0c699c84a2c352c95e42d0e94107d 100644
--- a/webkit/fileapi/file_system_directory_database.cc
+++ b/webkit/fileapi/file_system_directory_database.cc
@@ -714,7 +714,7 @@ bool FileSystemDirectoryDatabase::Init(RecoveryOption recovery_option) {
   }
   HandleError(FROM_HERE, status);
 
-  if (!status.IsCorruption())
+  if (!status.IsCorruption() && !status.IsIOError())

[kinuko, 2013/04/10 06:23:49]

Let me confirm. What other error types could we have here?

[tzik, 2013/04/10 06:49:20]

Status can be one of:
 - NotFound,
 - Corruption,
 - NotSupported,
 - InvalidArgument,
 - IOError.

NotFound is only when we look up the database,
Corruption and IOError are now handled here,
NotSupported and InvalidArgument looks irrelevant to handle here.

[kinuko, 2013/04/10 08:41:17]

Can we have a brief comment about them? Or at least should we have a comment why
we don't bail out for corruption and IO error case?

[tzik, 2013/04/10 10:59:49]

Done.

     return false;
 
   switch (recovery_option) {