diff options
| author | Brian Swetland <swetland@google.com> | 2010-09-23 16:06:23 -0700 |
|---|---|---|
| committer | Brian Swetland <swetland@google.com> | 2010-09-23 16:06:23 -0700 |
| commit | 4b8b59a7cd0e1413dcf9973c4bbd7eb65a444c4c (patch) | |
| tree | 34c08d53263881199349929b9a344d298e4cc036 /ext4_utils | |
| parent | 16abe7acb8f1dbeb8b9b1dc41061a53dcbfea851 (diff) | |
| download | extras-4b8b59a7cd0e1413dcf9973c4bbd7eb65a444c4c.tar.gz | |
zero the entire journal instead of just the first block
I'm seeing some weeeeird stuff with sparse ext4 images where
files sometimes seem to come back from the dead after reflashing,
etc. My crazy theory is they are hiding in the journal.
Colin humored me and pointed out how to ensure it's entirely
zero'd.
Change-Id: I4d14a2d4879c10540ef3c677ceb523bc061c1ec1
Diffstat (limited to 'ext4_utils')
| -rw-r--r-- | ext4_utils/ext4_utils.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ext4_utils/ext4_utils.c b/ext4_utils/ext4_utils.c index f34985f5..60a4da33 100644 --- a/ext4_utils/ext4_utils.c +++ b/ext4_utils/ext4_utils.c @@ -305,7 +305,7 @@ void ext4_create_journal_inode() u8 *journal_data = inode_allocate_data_extents(inode, info.journal_blocks * info.block_size, - info.block_size); + info.journal_blocks * info.block_size); if (!journal_data) { error("failed to allocate extents for journal data"); return; |