[f2fs-dev] [Bug 206551] New: Failed to initialize F2FS segment manager (-117)

* [f2fs-dev] [Bug 206551] New: Failed to initialize F2FS segment manager (-117)
@ 2020-02-16 19:14 bugzilla-daemon
  2020-02-16 19:15 ` [f2fs-dev] [Bug 206551] " bugzilla-daemon
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: bugzilla-daemon @ 2020-02-16 19:14 UTC (permalink / raw)
  To: linux-f2fs-devel

https://bugzilla.kernel.org/show_bug.cgi?id=206551

            Bug ID: 206551
           Summary: Failed to initialize F2FS segment manager (-117)
           Product: File System
           Version: 2.5
    Kernel Version: 5.5.3-gentoo
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: f2fs
          Assignee: filesystem_f2fs@kernel-bugs.kernel.org
          Reporter: stefan@konink.de
        Regression: No

Created attachment 287423
  --> https://bugzilla.kernel.org/attachment.cgi?id=287423&action=edit
Linux boot, root fs can't be mounted.

I am aware this bug report is done on a non-vanilla Gentoo based kernel, but
since I have seen it now twice in two days on two different kernel versions
5.4.13-gentoo and 5.5.3-gentoo I would like to document it upstream as well.
Not excluding a hardware failure.

I am running Linux on a Lenovo E485 machine having a AMD Ryzen 5 2500U
processor, which is quite problematic to resume after a memory suspend.
Therefore I use hibernation to a swap partition which most of the time allows
me to resume what I was working on. The disk is a Samsung SSD 840 EVO 500GB,
EXT0CB6Q. It wasn't used for quite a while but is now in use for about two
months without issues.

The day before yesterday I again hibernated my machine which kernel paniced
after resuming, the screen was still black, so I wouldn't have any information
on the topic. After restarting, my problems with F2FS, the filesystem for my
root partition, started.

I was able to boot using an Arch Linux ISO, and ran the F2FS-tools. fsck.f2fs
was unable to succeed when I requested to write "missing" files in ./lostfound.
Only when answering "No" the partition was repaired and could be mounted. I
remember that one of the causes flags was something like "Sudden loss of
power".

Today I have completely shutdown my machine using "poweroff". When I switched
the machine back on I had a similar experience as two days ago, my root
partition would mound with the same segment manager error. I again ran the
fsck.f2fs, this time not being prompted for missing files. Neither did it
mention anything similar like loss of power.

I wonder if the partition is fixed using the fsck.f2fs tool, considering the
output. If not, is this a gap in the implementation? Should this partition be
completely be copied, and then restored on a new f2fs partition? Or is it
expected that the file structure is "OK" after running the tool, and the fact
that two days in a row this happened was a coincidence?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

^ permalink raw reply	[flat|nested] 7+ messages in thread