[systemd-devel] systemd not in a steady state, although system is fine.

Lennart Poettering lennart at poettering.net
Wed Apr 1 06:38:21 PDT 2015


On Tue, 31.03.15 00:46, kenneth topp (toppk at bllue.org) wrote:

> > В Mon, 30 Mar 2015 19:35:21 -0400
> > "kenneth topp" <toppk at bllue.org> пишет:
> >
> >>
> >> Hi,
> >>
> >> 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?
> >>
> >
> > systemctl list-jobs
> >
> 
> Hi, Thanks, I see these jobs, I just don't know why the jobs are running. 
> They don't seem to be doing anything, and the unit doesn't offer any clue,
> and the block device is up.
> 
> ken
> 
> [root at static ~]# systemctl list-jobs
> JOB UNIT                       TYPE  STATE
> 208 dev-mapper-hp22.cfs.device start running
> 205 dev-mapper-hp27.cfs.device start running
> 199 dev-mapper-hp29.cfs.device start running
> 196 dev-mapper-hp30.cfs.device start running

Most likely those devices never show up properly? Most likely an
LVM/DM problem.

Please check with "udevadm info /dev/mapper/hp22.cfs" if the device
showed up properly in kernel/udev and carries the "systemd" udev tag.

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list