Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] sys-fs/f2fs-tools-1.12.0: breaks boot on f2fs root
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 808

PostPosted: Sat Nov 24, 2018 4:48 am    Post subject: [Solved] sys-fs/f2fs-tools-1.12.0: breaks boot on f2fs root Reply with quote

subj
Solution is disable fsck for rootfs.
Code:
rc default logging started at Sat Nov 24 11:29:13 2018

razerd            | * Starting razerd ...
rpc.pipefs        | * Setting up RPC pipefs ...
chronyd           | * Starting chronyd ...
fsck              | * Checking local filesystems  ...
 [ ok ]
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!
fsck              | * Filesystems couldn't be fixed
 [ !! ]
fsck              | * ERROR: fsck failed to start
 [ ok ]
 [ ok ]
urandom           | * ERROR: cannot start urandom as fsck would not start
netmount          | * ERROR: cannot start netmount as fsck would not start
cronie            | * ERROR: cannot start cronie as fsck would not start
localmount        | * ERROR: cannot start localmount as fsck would not start
mtab              | * ERROR: cannot start mtab as fsck would not start
bootmisc          | * ERROR: cannot start bootmisc as fsck would not start
elogind           | * ERROR: cannot start elogind as fsck would not start
net.eno1          | * ERROR: cannot start net.eno1 as fsck would not start
dbus              | * ERROR: cannot start dbus as fsck would not start
root              | * ERROR: cannot start root as fsck would not start
cupsd             | * ERROR: cannot start cupsd as fsck would not start
rpcbind           | * Starting rpcbind ...
 [ ok ]
rpc.idmapd        | * Starting idmapd ...
rpc.statd         | * Starting NFS statd ...
 [ ok ]
 [ ok ]
nfsclient         | * Starting NFS sm-notify ...
 [ ok ]
nfs               | * Mounting nfsd filesystem in /proc ...
 [ ok ]
nfs               | * Exporting NFS directories ...
nfs               |exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 30 (Read-only file system)
nfs               |exportfs: can't lock /var/lib/nfs/etab for writing
 [ !! ]
nfs               | * Starting NFS mountd ...
 [ ok ]
nfs               | * Starting NFS daemon ...
 [ ok ]
nfs               | * Starting NFS smnotify ...
 [ ok ]
local             | * Starting local ...
 [ ok ]

rc default logging stopped at Sat Nov 24 11:29:13 2018


Last edited by Perfect Gentleman on Tue Nov 27, 2018 7:21 am; edited 1 time in total
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Sat Nov 24, 2018 11:43 am    Post subject: Reply with quote

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.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 808

PostPosted: Sat Nov 24, 2018 12:04 pm    Post subject: Reply with quote

It fails 'cause
Code:
fsck              |Error: Failed to open the device!
fsck              | * Filesystems couldn't be fixed


Version 1.11.0-r1 works fine, no problems, no errors.

Quote:
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)

Yes, you're right.

I don't think it could be tagged as Solved, 'cause this is a bug.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 808

PostPosted: Sat Nov 24, 2018 12:06 pm    Post subject: Reply with quote

This is rc.log with f2fs-tools-1.11.0-r1
Quote:
rc boot logging started at Sat Nov 24 11:24:22 2018

modules | * Loading module vboxdrv ...
[ ok ]
modules | * Loading module vboxnetflt ...
[ ok ]
modules | * Loading module vboxnetadp ...
[ ok ]
modules | * Loading module vboxpci ...
[ ok ]
hwclock | * Setting system clock using the hardware clock [UTC] ...
[ ok ]
sysctl | * Configuring kernel parameters ...
hostname | * Setting hostname to HOSTNAME ...
loopback | * Bringing up network interface lo ...
[ ok ]
fsck | * Checking local filesystems ...
[ ok ]
[ ok ]
fsck |Info: Fix the reported corruption.
fsck |Info: Mounted device!
fsck |Info: Check FS only due to RO
fsck |Info: [/dev/sdd1] Disk Model: PLEXTOR PX-G256M1.06
fsck |Info: Segments per section = 1
fsck |Info: Sections per zone = 1
fsck |Info: sector size = 512
fsck |Info: total sectors = 500116111 (244197 MB)
fsck |Info: MKFS version
fsck | "Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018"
fsck |Info: FSCK version
fsck | from "Linux version 4.18.0-11-generic (buildd@lcy01-amd64-027) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #12-Ubuntu SMP Tue Oct 23 19:22:37 UTC 2018"
fsck | to "Linux version 4.19.4-gentoo (root@HOSTNAME) (gcc version 8.2.0 (Gentoo 8.2.0-r4 p1.5)) #1 ZEN SMP PREEMPT Fri Nov 23 22:15:59 +07 2018"
fsck |Info: superblock features = 0 :
fsck |Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
fsck |Info: total FS sectors = 500116104 (244197 MB)
fsck |Info: CKPT version = 7965081c
fsck |Info: Checked valid nat_bits in checkpoint
fsck |Info: checkpoint state = c5 : nat_bits crc compacted_summary unmount
fsck |
fsck |[FSCK] Unreachable nat entries [Ok..] [0x0]
fsck |[FSCK] SIT valid block bitmap checking [Ok..]
fsck |[FSCK] Hard link checking for regular file [Ok..] [0xe0]
fsck |[FSCK] valid_block_count matching with CP [Ok..] [0x6bb835]
fsck |[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0xebfb3]
fsck |[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0xebfb3]
fsck |[FSCK] valid_inode_count matched with CP [Ok..] [0xeb3ea]
fsck |[FSCK] free segment_count matched with CP [Ok..] [0x1a345]
fsck |[FSCK] next block offset is free [Ok..]
fsck |[FSCK] fixing SIT types
fsck |[FSCK] other corrupted bugs [Ok..]
fsck |
fsck |Done.
fsck |Info: Fix the reported corruption.
fsck |Info: [/dev/sda1] Disk Model: SAMSUNG MZ7WD2407W3Q
fsck |Info: Segments per section = 1
fsck |Info: Sections per zone = 1
fsck |Info: sector size = 512
fsck |Info: total sectors = 468860047 (228935 MB)
fsck |Info: MKFS version
fsck | "Linux version 4.16.6-gentoo (root@kubuntu) (gcc version 7.3.0 (Gentoo 7.3.0-r1 p1.1)) #1 ZEN SMP PREEMPT Tue May 1 18:28:05 +07 2018"
fsck |Info: FSCK version
fsck | from "Linux version 4.19.4-gentoo (root@HOSTNAME) (gcc version 8.2.0 (Gentoo 8.2.0-r4 p1.5)) #1 ZEN SMP PREEMPT Fri Nov 23 22:15:59 +07 2018"
fsck | to "Linux version 4.19.4-gentoo (root@HOSTNAME) (gcc version 8.2.0 (Gentoo 8.2.0-r4 p1.5)) #1 ZEN SMP PREEMPT Fri Nov 23 22:15:59 +07 2018"
fsck |Info: superblock features = 0 :
fsck |Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
fsck |Info: total FS sectors = 468860040 (228935 MB)
fsck |Info: CKPT version = 40e5095e
fsck |Info: checkpoint state = c5 : nat_bits crc compacted_summary unmount
fsck |Info: No error was reported
[ ok ]
root | * Remounting root filesystem read/write ...
[ ok ]
root | * Remounting filesystems ...
[ ok ]
mtab | * Updating /etc/mtab ...
swap | * Activating swap devices ...
mtab | * Creating mtab symbolic link
[ ok ]
[ ok ]
localmount | * Mounting local filesystems ...
[ ok ]
urandom | * Initializing random number generator ...
[ ok ]
bootmisc | * Creating user login records ...
[ ok ]
termencoding | * Setting terminal encoding [UTF-8] ...
dbus | * Starting dbus ...
[ ok ]
[ ok ]
keymaps | * Setting keyboard mode [UTF-8] ...
[ ok ]
keymaps | * Loading key mappings [us] ...
[ ok ]
elogind | * Starting elogind ...
[ ok ]

rc boot logging stopped at Sat Nov 24 11:24:42 2018
Back to top
View user's profile Send private message
Skinjob2707
n00b
n00b


Joined: 07 Aug 2013
Posts: 57

PostPosted: Sun Nov 25, 2018 1:48 pm    Post subject: Reply with quote

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?
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 808

PostPosted: Sun Nov 25, 2018 3:30 pm    Post subject: Reply with quote

Skinjob2707, the bug was closed as INVALID. I re-opened it.
https://bugs.gentoo.org/671786
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Mon Nov 26, 2018 12:19 pm    Post subject: Reply with quote

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.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 808

PostPosted: Mon Nov 26, 2018 3:59 pm    Post subject: Reply with quote

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

Quote:
It's true you didn't provide any good infos the dev could work on.

What kind of info could I provide?
Quote:
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 think that it is good info, really?
Quote:
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.

You know, I thought that he would collaborate, ask more info and send it to f2fs devs. But he decided to send me away to solve it on my own. And fuck yeah, I solved it.
Back to top
View user's profile Send private message
lost-distance
n00b
n00b


Joined: 10 Apr 2003
Posts: 73

PostPosted: Sat Mar 23, 2019 11:31 am    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 202
Location: Bavaria

PostPosted: Mon Apr 01, 2019 12:28 pm    Post subject: Reply with quote

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.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum