Systemd service file question (trying to start nilfs-cleanerd)

Question

My root file system is nilfs2. Yay!
But I can't get the cleanerd to auto-start.
According to the documentation, for root file systems, I need to run a manual command to start it.
I tried creating a unit (service) file to do this, but systemd doesn't seem to recognize it.
I create the file as /etc/systemd/system/nilfs-cleanerd.service, but I get an error trying to enable it.
I also have it as a "wants" to try to auto-run it.
Shell output, showing the file, and the command/error:
[root@robot1 /]# systemctl enable nilfs-cleanerd.service
Failed to issue method call: Invalid argument
[root@robot1 /]# cat /etc/systemd/system/nilfs-cleanerd.service
[Unit]
Description=Garbage collect NILFS segments
After=local-fs.target
[Service]
ExecStart=/sbin/nilfs_cleanerd
Type=simple
[Install]
Alias=nilfs-cleanerd.service
WantedBy=local-fs.target.wants
[root@robot1 /]#
So, how do I debug this error? There's no "-v" option to systemctl to get more verbose error messages that might give a hint about where in the operation it fails.
Also, there seems to be a cleanerd running somehow:
[root@robot1 /]# ps alx | grep ni[l]
1 0 222 2 20 0 0 0 nilfs_ S ? 0:03 [segctord]
4 0 223 1 20 0 14692 864 wq_sle Ss ? 0:00 /sbin/nilfs_cleanerd -n /dev/sda1 /
[root@robot1 /]#
but nilfs-clean doesn't find it:
[root@robot1 /]# nilfs-clean
No cleaner found on /dev/sda1.
[root@robot1 /]#
so it may be that my problem is related to nilfs-clean rather than the systemctl command. But I still want to understand how to debug this systemctl error.

Answer 1

tomk wrote:Finally if you think the wiki is not clear enough on what goes where, you can improve it yourself.
I'd be happy to improve it, once I find the authoritative source that tells me what the rule is.
You're not actually answering the question, though, unless I'm supposed to read between the lines.
Are you saying that locally defined services should, in fact, have their files live in /etc/systemd/system ? Because when I select particular services, symlinks get generated in /etc/systemd/system. Here's the output of "ls -l /etc/systemd/system" on my machine:
[jwatte@robot1 Onyx]$ ls -l /etc/systemd/system
total 40
-rw-r--r-- 1 root root 1662 Dec 14 05:00 [email protected]
lrwxrwxrwx 1 root root 41 Dec 14 05:05 default.target -> /usr/lib/systemd/system/multi-user.target
lrwxrwxrwx 1 root root 36 Dec 14 04:50 display-manager.service -> /usr/lib/systemd/system/lxdm.service
drwxr-xr-x 2 root root 4096 Dec 14 05:01 getty.target.wants
drwxr-xr-x 2 root root 4096 Dec 30 15:57 local-fs.target.wants
drwxr-xr-x 2 root root 4096 Dec 29 20:19 multi-user.target.wants
-rwxr-xr-x 1 root root 191 Dec 30 15:57 nilfs-cleanerd.service
drwxr-xr-x 2 root root 4096 Dec 29 20:19 printer.target.wants
drwxr-xr-x 2 root root 4096 Dec 29 20:19 sockets.target.wants
drwxr-xr-x 2 root root 4096 Nov 22 07:21 sysinit.target.wants
[jwatte@robot1 Onyx]$
Note the symlinks for default.target and display-manager.service. Then again, [email protected] is a file living in this directory.
The problem then becomes: Why do I get the error listed at the beginning of this post?
Here's the output of ls -l on local-fs.target:
[jwatte@robot1 Onyx]$ ls -l /etc/systemd/system/local-fs.target.wants/
total 4
lrwxrwxrwx 1 root root 42 Dec 30 15:57 nilfs-cleanerd.service -> /etc/systemd/system/nilfs-cleanerd.service
[jwatte@robot1 Onyx]$
Last edited by jwatte (2013-01-01 22:52:01)