cachefilesd not starting with CONFIG_CACHEFILES=y

[Christian Kujau]

Binary package hint: cachefilesd

I've compiled a custom kernel and /etc/init.d/cachefilesd won't start:

# service cachefilesd start
 * Starting FilesCache daemon cachefilesd
FATAL: Module cachefiles not found.
Failed to load fscache module,

The initscript tries to "modrobe cachefiles" (but erroneously complains about the "fscache module", which is another module), which is compiled statically in my kernel:
CONFIG_FSCACHE=y
CONFIG_CACHEFILES=y
CONFIG_NFS_FSCACHE=y

Manually starting cachefilesd works fine. I'm not sure if initscripts should struggle with modules at all. E.g. /etc/init.d/networking doesn't load NIC modules too. Think about the module madness /etc/init.d/lm-sensors would have to perform.

# grep -ilr modprobe /etc/init.d/
/etc/init.d/powernowd
/etc/init.d/cachefilesd.ubuntu

As long as /etc/modules is not obsolete, I think the modprobe stuff can be left out of /etc/init.d/cachefilesd and therefore I propose the attached patch.

[Christian Kujau (christiank)]

bump!

[ski (skibrianski)]

I've found cachefilesd to be fragile in general, but most recently the source of the problem that I had is that I had the backports repository enabled. The linux kernels backported from quantal (3.5.0.X) displays exactly this behavior with cachefilesd, but the linux kernels from precise "proper" (3.2.0.X) work just fine.

If you have linux-generic-lts-quantal installed, remove it, reboot, and see if that fixes things for you - it did for me!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Kujau (christiank)]

Ubuntu Linux switched to systemd ever since, this report is no longer relevant.