Commit bde582b2 authored by Chris Fries's avatar Chris Fries Committed by Jaegeuk Kim

f2fs: continue to mount after failing recovery

When unable to roll forward the journal, we shouldn't bail out and
not mount, we should continue to attempt the mount.  Bad recovery data
is likely unrecoverable at this point, and requiring the user to try
to mount again doesn't solve any issues.
Signed-off-by: default avatarChris Fries <C.Fries@motorola.com>
Reviewed-by: default avatarRussell Knize <rknize2@motorola.com>
Reviewed-by: default avatarJason Hrycay <jason.hrycay@motorola.com>
Signed-off-by: default avatarJaegeuk Kim <jaegeuk.kim@samsung.com>
parent 531ad7d5
...@@ -669,10 +669,9 @@ static int f2fs_fill_super(struct super_block *sb, void *data, int silent) ...@@ -669,10 +669,9 @@ static int f2fs_fill_super(struct super_block *sb, void *data, int silent)
/* recover fsynced data */ /* recover fsynced data */
if (!test_opt(sbi, DISABLE_ROLL_FORWARD)) { if (!test_opt(sbi, DISABLE_ROLL_FORWARD)) {
err = recover_fsync_data(sbi); err = recover_fsync_data(sbi);
if (err) { if (err)
f2fs_msg(sb, KERN_ERR, "Failed to recover fsync data"); f2fs_msg(sb, KERN_ERR,
goto free_root_inode; "Cannot recover all fsync data errno=%ld", err);
}
} }
/* After POR, we can run background GC thread */ /* After POR, we can run background GC thread */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment