[Solved] sys-fs/f2fs-tools-1.12.0: breaks boot on f2fs root

Perfect Gentleman · Veteran Joined: 18 May 2014 Posts: 1249

subj
Solution is disable fsck for rootfs.

krinn · Watchman Joined: 02 May 2003 Posts: 7470

Why it fails? isn't f2fs-tools providing fsck part for f2fs? If so, fsck should be happy to run it.
And second, how you have disable it? (i think thru fstab by setting sixth field entry to 0 ; but that's something people may wish to know)

Your post seems more "informative" than a "request support" one, however, you should have set the title SOLVE if you intend to only provide information and help people getting the solve, and if it was what you were wishing to do, you should had provide some few more information or do it more clearly.

Perfect Gentleman · Veteran Joined: 18 May 2014 Posts: 1249

It fails 'cause

Perfect Gentleman · Veteran Joined: 18 May 2014 Posts: 1249

This is rc.log with f2fs-tools-1.11.0-r1

Skinjob2707 · n00b Joined: 07 Aug 2013 Posts: 57

I'm also experiencing this issue. When I reverted to f2fs-tools-1.11.0-r1 the problem went away. My system is running systemd. How do I produce similar output to the above entries reporting the contents of rc.log using systemd? I don't see a bug report on bugs.gentoo.org. Is someone going to create one?

Perfect Gentleman · Veteran Joined: 18 May 2014 Posts: 1249

Skinjob2707, the bug was closed as INVALID. I re-opened it.
https://bugs.gentoo.org/671786

krinn · Watchman Joined: 02 May 2003 Posts: 7470

It's true you didn't provide any good infos the dev could work on.
But he is an asshole still that dismiss your bug without real reason, he should be the one that dig the problem and once find the problem in f2fs-tools is not coming from gentoo but the program itself, tell upstream about it or send you to upstream.

He has chose to sent you upstream, while upstream may just kick your ass because it work for them, or because many other distros have package that version and no user report the issue ; with the bad effect of showing gentoo-dev are not doing the work except packaging (badly) something.

Dunno what you could do, you might tell him at least arch linux is using that version too and you cannot find any bug report about it.
You could also argue that since 1.12 release, upstream has update it, but not any fix for that problem (some android update).
Base on this: it "should" work for archlinux, it work for upstream (else newer update would had been the fix) -> gentoo specific

But he has reply 2 times already to go upstream and he is now in a bullhead loop, honestly your best hope now in my opinion would be that Skinjob2707 would create a dup bug report (on purpose) in order to gave him another 3rd chance to get out of his loop.
Please guys, provide minimal infos, you're not suppose to be able to debug everything yourself as user, but emerge --info from your system is something any user could provide easy.

Perfect Gentleman · Veteran Joined: 18 May 2014 Posts: 1249

krinn, I wrote to the dev-team. And they confirmed that bug, then send me patch which I've tested.

lost-distance · n00b Joined: 10 Apr 2003 Posts: 73

I hit the same problem yesterday after merging the newly stable sys-fs/f2fs-tools-1.12.0-r1 package.

I fixed it by applying the following patch from git.kernel.org, titled "mkfs.f2fs: allow to open mounted device":

https://git.kernel.org/pub/scm/linux/kernel/git/chao/f2fs-tools.git/commit/?h=dev-test&id=9a5116cfab7258efc6347d93d18989c638f3f9bf

tomtom69 · Posted: Mon Apr 01, 2019 12:28 pm Post subject:

I got the same error message after the update of f2fs-tools, but only sometimes.
On my system the setting rc_parallel="YES" in /etc/rc.conf triggered this error (I had set this to "YES" years ago because it gave boot speed improvement).
After setting rc_parallel="NO" everything went normal again.