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: Chris Fries <[email protected]>
Reviewed-by: Russell Knize <[email protected]>
Reviewed-by: Jason Hrycay <[email protected]>
Signed-off-by: Jaegeuk Kim <[email protected]>

diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index cd0e89a1ff8f18c4c51668f2aec0f2fda89b43c1..392dba26414a0ebb35c44127674e2b27adf3091f 100644 (file)
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -669,10 +669,9 @@ static int f2fs_fill_super(struct super_block *sb, void *data, int silent)
        /* recover fsynced data */
        if (!test_opt(sbi, DISABLE_ROLL_FORWARD)) {
                err = recover_fsync_data(sbi);
-               if (err) {
-                       f2fs_msg(sb, KERN_ERR, "Failed to recover fsync data");
-                       goto free_root_inode;
-               }
+               if (err)
+                       f2fs_msg(sb, KERN_ERR,
+                               "Cannot recover all fsync data errno=%ld", err);
        }
 
        /* After POR, we can run background GC thread */