Handle inconsistency between DB and Files

webkit/fileapi/sandbox_mount_point_provider.cc

Index: webkit/fileapi/sandbox_mount_point_provider.cc
diff --git a/webkit/fileapi/sandbox_mount_point_provider.cc b/webkit/fileapi/sandbox_mount_point_provider.cc
index 920a8209831775d62b745735eac15f0e39838f7f..5d61a75fbb91a0176867c6addebfd80389339309 100644
--- a/webkit/fileapi/sandbox_mount_point_provider.cc
+++ b/webkit/fileapi/sandbox_mount_point_provider.cc
@@ -620,6 +620,11 @@ void SandboxMountPointProvider::EndUpdateOriginOnFileThread(
   FileSystemUsageCache::DecrementDirty(usage_file_path);
 }
 
+void SandboxMountPointProvider::ScheduleRecalculateUsage(
+    const GURL& origin_url, fileapi::FileSystemType type) {
+  StartUpdateOriginOnFileThread(origin_url, type);

[ericu, 2011/08/17 00:54:08]

This doesn't actually start an update--it just marks the file to say there's one
in progress.

[tzik, 2011/08/18 08:02:26]

Actually, what I want to do in here is to increment the dirty count for the
origin and the type.
It'll force SMPP to recalculate usage at next initialization time.

[ericu, 2011/08/19 04:05:56]

What about just deleting the usage cache file?  Or would that cause other
problems?

[tzik, 2011/08/23 04:13:13]

If some write-operation are running, they breaks dirty count at completion
without .usage file.
How about adding validity flag to .usage to mark it invalid, like patchset 5?

+}
+
 FileSystemFileUtil* SandboxMountPointProvider::GetFileSystemFileUtil() {
   return sandbox_file_util_.get();
 }