Commit bde582b2 authored May 02, 2013 by Chris Fries Committed by Jaegeuk Kim May 08, 2013

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 <C.Fries@motorola.com>
Reviewed-by: Russell Knize <rknize2@motorola.com>
Reviewed-by: Jason Hrycay <jason.hrycay@motorola.com>
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>

parent 531ad7d5

fs/f2fs/super.c

+3 −4

Original line number	Diff line number	Diff line
		@@ -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 */