Index: chrome/browser/extensions/api/image_writer_private/destroy_partitions_operation.cc |
diff --git a/chrome/browser/extensions/api/image_writer_private/destroy_partitions_operation.cc b/chrome/browser/extensions/api/image_writer_private/destroy_partitions_operation.cc |
index 1ad6d98bc9c1fc6ceddf5613ea898073155691c6..55a146801ad5ce10e62773c828819eb74e8b2766 100644 |
--- a/chrome/browser/extensions/api/image_writer_private/destroy_partitions_operation.cc |
+++ b/chrome/browser/extensions/api/image_writer_private/destroy_partitions_operation.cc |
@@ -10,10 +10,10 @@ |
namespace extensions { |
namespace image_writer { |
-// Number of bytes for the maximum partition table size. By wiping this many |
-// bytes we can essentially guarantee the header and associated information will |
-// be wiped. See http://crbug.com/328246 for more information. |
-const int kPartitionTableSize = 1 * 1024; |
+// Number of bytes for the maximum partition table size. GUID partition tables |
+// reside in the second sector of the disk. Disks can have up to 4k sectors. |
+// See http://crbug.com/328246 for more information. |
+const int kPartitionTableSize = 2 * 4096; |
DestroyPartitionsOperation::DestroyPartitionsOperation( |
base::WeakPtr<OperationManager> manager, |