Hi, > Am 27.11.2018 um 01:08 schrieb Jaegeuk Kim <jaeg...@kernel.org>: > On 11/26, Michael Laß wrote: >> >>> Am 26.11.2018 um 15:09 schrieb Chao Yu <c...@kernel.org>: >>> But the problem here is even .i_gc_failures's value is one which was >>> initialized >>> duing inode creation by old kernel, and it never be increased by GC flow, we >>> will still trigger such fix in fsck. I think it's not necessary, anyway, >>> let me >>> send one patch to fix it. >> >> This is a very likely cause. The filesystems are both from early 2015, so >> probably were used with Linux 3.18 or 3.19 at that time. > > Just in case, is this Android device? If you don't use ioctl(F2FS_PIN_FILE), > this onetime fix wont' hurt any filesystem metadata.
no, it’s used on a regular GNU/Linux system, a Raspberry Pi running Arch Linux ARM to be more specific. The kernel is currently still at version 4.14.83 so as far as I can see that ioctl isn’t even available. I guess I’ll see these messages again after new files have been created by that old kernel but should not worry about it. Best regards, Michael _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
