I'm using nilfs2 on my rootfs. nilfs2 needs a garbage collection deamon runnig to clean up old snapshots and free up some disk space. With newer udev /dev/root isn't created anymore, but my devices are still mount like this: wloczykij ~ # mount rootfs on / type rootfs (rw) /dev/root on / type nilfs2 (rw,relatime) Revelant part of strace analysis on linux-nilfs [1] and the whole thread [2] and similar issue reported by other user [3]. Also on linux-nilfs I did some quick and dirty check [4]: "I checked udev in the first place. udev-182-r3 (from Gentoo portage tree) with udev-init-scripts-10 creates /dev/root. udev-186 with udev-init-scripts-12 doesn't." [1] http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2436 [2] http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2419 [3] http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2491 [4] http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2439 Reproducible: Always Actual Results: nilfs_cleanerd not running because /dev/root is missing. Expected Results: /dev/root is created again or... mounts are per device? /dev/sdXY on / type foofs (opts) PS Why Gentoo uses /dev/root anyway?
I think this is more udev related then nilfs-utils maintainers. Similar bugs are already on bugzilla (bug #381761, bug #427818 and bug #390519).
Do you get this after upgrading to udev 190?
*** This bug has been marked as a duplicate of bug 390519 ***
This is not a udev issue. Please see the tracker this bug blocks now for more information about how you may be able to fix your package. Thanks, William
I just investigated the discussion again and I've concluded that nilfs_cleanerd itself dosen't depend on /dev/root. It failes because the root file system is accidently mounted using /dev/root On my box, /proc/mounts give me: rootfs / rootfs rw 0 0 ... /dev/sda2 / ext4 rw,noatime,data=ordered 0 0 ... It should also be the same for nilfs. Piotr, how do you write your root entry in your /etc/fstab ?
(In reply to comment #5) > I just investigated the discussion again and I've concluded that > nilfs_cleanerd itself dosen't depend on /dev/root. It failes because the > root file system is accidently mounted using /dev/root > > On my box, /proc/mounts give me: > > rootfs / rootfs rw 0 0 > ... > /dev/sda2 / ext4 rw,noatime,data=ordered 0 0 > ... > > It should also be the same for nilfs. > > Piotr, how do you write your root entry in your /etc/fstab ? Sorry, missed mail notification. UUID=1aa9e6fb-cf7d-45bd-bbfb-08110a8840b7 / nilfs2 noatime,nodiratime,rw 0 1 Well, i suppose i can remove the no{,dir}atime options anyway, but that's not the issue here. maszn ~ # mount | grep root rootfs on / type rootfs (rw) /dev/root on / type nilfs2 (rw,noatime,nodiratime)
It seems like bug 339472 is relevant.
(In reply to comment #7) > It seems like bug 339472 is relevant. No, it isn't. Bug #339472 is about improper mounting of rootfs which in case of nilfs2 prevents running of nilfs_cleanerd and a user needs to run the daemon on his/her own. A simple change in /etc/init.d/root fixes the bug #339472 without special handling of nilfs2. This bug is about the situation that the daemon returns without forking a background process if /dev/root doesn't exist. Even if a user starts the daemon from the command line, nothing happens, the program silently returns.
udev-init-scripts-25 is creating /dev/root again for non-btrfs file systems but it doesn't mean this bug can be closed in fact, the symlink is there only temporary until bugs like this one have been solved
