Hi Tim, On Jan 20, 2013, at 9:51 AM, Tim Benham wrote: > After upgrading from the 3.5.0 to the 3.7.2 kernel I cannot get > nilfs_cleanerd to start. Trying to start it causes the following lines > to be appended to the system log. > > Jan 20 16:36:07 gigasys nilfs_cleanerd[2584]: start > Jan 20 16:36:07 gigasys nilfs_cleanerd[2584]: cannot open nilfs on > (null): No such file or directory > Jan 20 16:36:07 gigasys nilfs_cleanerd[2584]: cannot create cleanerd > on (null): No such file or directory > Jan 20 16:36:07 gigasys nilfs_cleanerd[2584]: shutdown > > My root file system is nilfs2. Cleanerd has never started on mount. I > worked around this by creating a local.d script that starts it. Then > this stopped working. I was able to get it going again by modifying my > script to create a /dev/root symlink. Now I cannot get it to start at > all. Giving it the root device explicitly doesn't work either > > > # nilfs_cleanerd /dev/sda2 > Jan 20 16:41:19 gigasys nilfs_cleanerd[2648]: start > Jan 20 16:41:19 gigasys nilfs_cleanerd[2648]: cannot open nilfs on > /dev/sda2: No such file or directory > Jan 20 16:41:19 gigasys nilfs_cleanerd[2648]: cannot create cleanerd > on /dev/sda2: No such file or directory > Jan 20 16:41:19 gigasys nilfs_cleanerd[2648]: shutdown > # ls -l /dev/sda2 > brw-rw---- 1 root disk 8, 2 Jan 20 16:18 /dev/sda2 > > mount -t nilfs2 -o remount /dev/sda2 / produces an identical set of messages. It looks like you have troubles with udev after upgrade. Could you share strace output of nilfs_cleanerd trying to start? Could you share fstab file content on your system? With the best regards, Vyacheslav Dubeyko. > -- > To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
