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
