[systemd-devel] systemd not in a steady state, although system is fine.
toppk at bllue.org
Mon Mar 30 16:35:21 PDT 2015
My system appears healthy, but for some reason systemd not in a good state.
>From the commands and their output, I have two concerns.
1) why is the state "starting" and not finished?
2) what are these "jobs" that are running?
This happens to be four luks partitions that go into a btrfs filesystem
(which is mounted fine). I also have another btrfs filesystem made of two
luks partitions that aren't showing this issue (and is also mounted fine)
Any documentation or pointers as to how to debug would be nice. running
[root at static ~]# systemctl status | head -3
Jobs: 4 queued
[root at static ~]# systemctl --state=dead
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
dev-mapper-hp22.cfs.device loaded inactive dead start
dev-mapper-hp28.cfs.device loaded inactive dead start
dev-mapper-hp29.cfs.device loaded inactive dead start
dev-mapper-hp30.cfs.device loaded inactive dead start
LOAD = Reflects whether the unit definition was properly loaded. ACTIVE
= The high-level unit activation state, i.e. generalization of SUB. SUB
= The low-level unit activation state, values depend on unit type. JOB
= Pending job for the unit.
4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
[root at static ~]# btrfs fi show
Label: 't2' uuid: cf65d309-0792-4f6b-b802-8e99509410b6
Total devices 2 FS bytes used 672.00KiB
devid 1 size 447.13GiB used 2.03GiB path /dev/mapper/hp30.cfs
devid 2 size 447.13GiB used 2.01GiB path /dev/mapper/hp31.cfs
Label: 'tm' uuid: 95fbdd87-16f0-4297-a847-ef0ea2cdcbf2
Total devices 4 FS bytes used 8.00TiB
devid 2 size 1.82TiB used 1.76TiB path /dev/mapper/hp22.cfs
devid 3 size 2.73TiB used 2.65TiB path /dev/mapper/hp27.cfs
devid 4 size 1.82TiB used 1.77TiB path /dev/mapper/hp28.cfs
devid 5 size 2.73TiB used 2.54TiB path /dev/mapper/hp29.cfs
More information about the systemd-devel