summaryrefslogtreecommitdiffstats
path: root/scripts/dtc
diff options
context:
space:
mode:
authorChris Fries <C.Fries@motorola.com>2013-05-02 16:07:34 -0500
committerJaegeuk Kim <jaegeuk.kim@samsung.com>2013-05-08 19:54:19 +0900
commitbde582b225e98fe9e35cd67e4cb4406a6f85ae3e (patch)
tree5c6bd1d89759315d95126900c84a24a30b7f5ecf /scripts/dtc
parent531ad7d58c6476c5856653448b4c7d26427502b4 (diff)
downloadlinux-bde582b225e98fe9e35cd67e4cb4406a6f85ae3e.tar.bz2
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>
Diffstat (limited to 'scripts/dtc')
0 files changed, 0 insertions, 0 deletions