Doug / smarc-fsl-linux-kernel

Download as
Browse Code ยป

Commit bde582b225e98fe9e35cd67e4cb4406a6f85ae3e

Authored by Chris Fries
Committed by Jaegeuk Kim
1 parent 531ad7d58c
Exists in smarc-l5.0.0_1.0.0-ga and in 5 other branches imx_3.10.17_1.0.1_ga, imx_3.10.53_1.1.0_ga, imx_3.14.28_1.0.0_ga, smarc-imx_3.10.53_1.1.0_ga, smarc-imx_3.14.28_1.0.0_ga

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>

Showing 1 changed file with 3 additions and 4 deletions Side-by-side Diff

... ... @@ -669,10 +669,9 @@
669 669 /* recover fsynced data */
670 670 if (!test_opt(sbi, DISABLE_ROLL_FORWARD)) {
671 671 err = recover_fsync_data(sbi);
672   - if (err) {
673   - f2fs_msg(sb, KERN_ERR, "Failed to recover fsync data");
674   - goto free_root_inode;
675   - }
  672 + if (err)
  673 + f2fs_msg(sb, KERN_ERR,
  674 + "Cannot recover all fsync data errno=%ld", err);
676 675 }
677 676  
678 677 /* After POR, we can run background GC thread */