On Thu, Dec 2, 2021 at 2:06 PM Gordon Messmer <gordon.messmer(a)gmail.com>
wrote:
On 12/1/21 18:03, murph nj wrote:
>
> lsof showed nothing that I could see.
Nothing, or nothing interesting? I'd expect you to at least see the CWD
of the debug shell.
Got another opportunity, redirected lsof /home and lsof /other to files,
and there was no output.
> The stop job rotates between four mounted volumes, and the
> lvm2-monitor.service.
In the past, I've seen lvm2-monitor behave badly in reaction to logical
volumes (block devices) used for VMs that used LVM internally. Do you
have any logical volumes that aren't used for those four mounted volumes?
No LVM, as mentioned earlier
> systemctl status doesn't seem to display much, but the stop job (and
> cylon eye) keep overwriting everything, making it really hard to see
> the output.
Several suggestions: Chris suggested that you check "systemctl
list-jobs". The contents of /proc/mounts might be interesting. I'd run
"lsof /path" where path is the longest mount point path of the volumes
still listed in /proc/mounts.
I did get output from systemctl-list-jobs (edited lightly)
JOB UNIT
TYPE STATE
5788 poweroff.target
start waiting
6039 systemd-cryptsetup(a)luks\x2dshome.service stop
running
5790 shutdown.target
start waiting
6031 final.target
start waiting
6068 systemd-cryptsetup(a)luks\x2de<snip>8.service stop
running
6055 systemd-cryptsetup(a)luks\x2dsother.service stop
running
6013 lvm2-monitor.service
stop running
6047 systemd-cryptsetup(a)luks\x2d2<snip>3.service stop
running
6032 umount.target
start waiting
5789 systemd-poweroff.service
start waiting
10 jobs listed.