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

[Andrei Borzenkov]

On Tue, Mar 31, 2015 at 7:46 AM, 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
>
> 4 jobs listed.
>

Do you have any mount points or crypto units using these devices?

What

systemctl show -p RequiredBy -p WantedBy dev-mapper-hp22.cfs.device
dev-mapper-hp27.cfs.device dev-mapper-hp29.cfs.device
dev-mapper-hp30.cfs.device

show?

> [root at static ~]# systemctl status dev-mapper-hp22.cfs.device
> ● dev-mapper-hp22.cfs.device
>    Loaded: loaded
>   Drop-In: /run/systemd/generator/dev-mapper-hp22.cfs.device.d
>            └─90-device-timeout.conf
>    Active: inactive (dead)
>
>
> [root at static ~]# lsblk /dev/mapper/hp27.cfs
> NAME     MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
> hp27.cfs 253:7    0  2.7T  0 crypt
>