inotify on unionfs-fuse watches the base filesystem, not the cow filesystem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unionfs-fuse (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: upstart
Ubuntu Version:
Description: Ubuntu 9.10
Release: 9.10
Package Version:
upstart:
Installed: 0.6.3-10
Candidate: 0.6.3-10
Version table:
*** 0.6.3-10 0
500 http://
100 /var/lib/
Expected:
Services start when installed only on the copy-on-write (cow) system
Result:
Services only start when installed on the base system
Details:
We use a cow filesystem using unionfs-fuse and if the user installs any services that rely on upstart they are unable to be started through upstart facilities such as service, start, or initctl. If installed on the base system it works fine.
boot into cow leaves the system like this ->
unionfs-fuse on / type fuse.unionfs-fuse (rw,errors=
/dev/sda1 on /.oldroot type ext4 (rw)
After doing something like, apt-get install dbus. dbus is unable to start with service returning this message: start: Unknown job: dbus
If I copy the dbus.conf from /etc/init/dbus.conf -> /.oldroot/
dbus can be started normally.
The cow is started as a pre-script on mountall.conf. Perhaps there is a better location? I'm trying to make the process of adding / removing cow as painless as possible.
This is most likely a bug in unionfs-fuse, but first could you check something for me:
if instead of copying the file to the old root, you run:
initctl reload- configuration
does it then see the dbus job?