From: Chao Yu <chao@kernel.org>
To: Perfect Gentleman <perfect007gentleman@gmail.com>,
Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Bug in f2fs-tools-1.12.0
Date: Mon, 26 Nov 2018 21:35:22 +0800 [thread overview]
Message-ID: <b1c95e28-23ea-cd75-5b9c-310a817eb854@kernel.org> (raw)
In-Reply-To: <0417cc7e-b1ba-cc3d-e5f6-bbb989000faa@GMail.com>
Hi Perfect Gentleman,
On 2018-11-26 19:11, Perfect Gentleman wrote:
> Hi Chao
>
> What patch do you mean?
I mean
https://git.kernel.org/pub/scm/linux/kernel/git/chao/f2fs-tools.git/commit/?h=dev-test&id=a6160c3e21f43b89b49802cc4a956d1c4b65ae44
Thanks,
>
> Redards
>
> P.S. It's reply to all :)
>
> On 11/26/18 5:52 PM, Chao Yu wrote:
>> Hi Perfect Gentleman,
>>
>> Thanks for the report.
>>
>> On 2018/11/25 13:24, Perfect Gentleman wrote:
>>> Hi f2fs-team,
>>>
>>> there is bug: fsck.f2fs cannot check read-only filesystem. But 1.11.0
>>> can do that.
>>>
>>> fsck |Info: Fix the reported corruption.
>>> fsck |Info: Mounted device!
>>> fsck |Info: Check FS only due to RO
>>> fsck |Error: Failed to open the device!
>> I guess this is due to below commit, which stop opening device in
>> f2fs-tools if the device has already been opened by other one, like mount.
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=eb9d8037ed3b37a647d514470f1a1df91daedb64
>>
>>
>> I tried e2fsprogs, w/o -f option, the result is the same:
>>
>> fsck 1.44.4 (18-Aug-2018)
>> e2fsck 1.44.4 (18-Aug-2018)
>> /dev/zram0 is mounted.
>> e2fsck: Cannot continue, aborting.
>>
>> But still we can trigger forced fsck.ext4 by using -f option.
>>
>> Could you have a try with following patch?
>>
>> [PATCH] fsck.f2fs: allow to fsck readonly image w/ -f option
>>
>> Thanks,
>>
>>> fsck | * Filesystems couldn't be fixed
>>> [ !! ]
>>> fsck | * ERROR: fsck failed to start
>>>
>>> Regards,
>>> Alex
>>>
>>>
>>>
>>> _______________________________________________
>>> Linux-f2fs-devel mailing list
>>> Linux-f2fs-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>>>
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2018-11-26 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 5:24 Bug in f2fs-tools-1.12.0 Perfect Gentleman
2018-11-26 10:52 ` Chao Yu
2018-11-26 11:11 ` Perfect Gentleman
2018-11-26 13:35 ` Chao Yu [this message]
2018-11-26 13:47 ` Perfect Gentleman
2018-11-26 13:50 ` Chao Yu
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=b1c95e28-23ea-cd75-5b9c-310a817eb854@kernel.org \
--to=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=perfect007gentleman@gmail.com \
--cc=yuchao0@huawei.com \
/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).