From: Luke Dashjr <luke@dashjr.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Corrupt F2FS partition - fsck is useless
Date: Tue, 28 Aug 2018 07:49:27 +0000 [thread overview]
Message-ID: <201808280749.28098.luke@dashjr.org> (raw)
In-Reply-To: <20180828073735.GD29049@jaegeuk-macbookpro.roam.corp.google.com>
On Tuesday 28 August 2018 07:37:35 Jaegeuk Kim wrote:
> Are you using dm-crypt under f2fs?
No.
> v3.10 is too much old, and I quit to backport recent patches as well.
> Is there a chance to upgrade the kernel?
The 3.10 was the Android/LineageOS phone that couldn't even boot.
I'm doing all the data recovery attempts on 4.17.11.
Thanks,
Luke
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2018-08-28 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 4:31 Corrupt F2FS partition - fsck is useless Luke Dashjr
2018-08-24 13:08 ` Chao Yu
2018-08-24 14:38 ` Luke Dashjr
2018-08-24 15:59 ` Chao Yu
2018-08-28 9:28 ` Chao Yu
2018-08-28 9:47 ` Luke Dashjr
2018-08-28 10:34 ` Chao Yu
2018-08-28 7:37 ` Jaegeuk Kim
2018-08-28 7:49 ` Luke Dashjr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201808280749.28098.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).