[systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

Colin Walters walters at verbum.org
Tue Feb 17 11:25:01 PST 2015


On Tue, Feb 17, 2015, at 01:47 PM, Colin Walters wrote:
> I'm trying to track down a relatively recent change in systemd
> which broke OSTree; see https://bugzilla.gnome.org/show_bug.cgi?id=743891
> 
> Systemd started to stop sysroot.mount, and this patch should help
> me debug why at least.

Running with this patch, I see:

systemd[1]: Unit sysroot.mount is bound to inactive unit dev-vda3.device. Stopping, too.

But, dev-vda3.device is active:

* dev-vda3.device - /dev/vda3
   Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:07.0-virtio2-block-vda-vda3.device
   Loaded: loaded
   Active: active (plugged) since Tue 2015-02-17 19:15:29 GMT; 6min ago
   Device: /sys/devices/pci0000:00/0000:00:07.0/virtio2/block/vda/vda3

I'll see if I can get more information out of debug logging.


More information about the systemd-devel mailing list