Comment # 6 on bug 1226043 from Luis Henriques

(In reply to Jonas Kvinge from comment #5)
> Thank you. After I added "fsck.mode=force" I could no longer reproduce the
> issue when cutting power, as soon as I removed "fsck.mode=force" it's stuck
> almost every time the power is cut.
> 
> Even if you fixed the issue, is it a good idea to keep fsck.mode=force for
> machines that are often shut down by cutting power? I assume it does not
> hurt, since it only takes a few seconds more when booting.

I guess that what 'fsck.mode=force' will do is to run e2fsck with '-f' even if
the filesystem seems to be clean (but I'm not familiar with the details on how
this parameter is handled, probably by systemd).

In general, forcing the filesystem check shouldn't be needed in most cases, but
it should also be harmless.  On the other hand, my patch to e2fsck is to
actually force it to do a full check in the presence of the orphan files inode.
 So using that kernel parameter seems to be a good workaround to the issue.

(In the meantime, I haven't had any feedback on my patch yet.)