#991550 lvm2: blk-availability.service sometimes causes early filesystem unmounts.

Package:
lvm2
Source:
lvm2
Description:
Linux Logical Volume Manager
Submitter:
Agustin Martin
Date:
2021-08-02 22:30:02 UTC
Severity:
normal
#991550#5
Date:
2021-07-27 09:56:30 UTC
From:
To:
Dear Maintainer,

Sometimes there is a weird behavior causing some filesystems to be unmounted
too early, when they are still needed. I have only found this problem in a
box with lvm on top of RAID, but not in other boxes using lvm. Seems that
this problem is related to lvm2.

From redhat bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1701234)

  The blk-availability.service unit is activated automatically when
  multipathd is enabled, even if multipathd is finally not used.
  This leads to the blk-availability service to unmount file systems
  too early, breaking unit ordering and leading to shutdown issues of
  custom services requiring some mount points.

This has been reported upstream as https://github.com/lvmteam/lvm2/issues/18
and also to Ubuntu launchpad as
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859

In the problematic box I have temporatily added
"After=blk-availability.service" and seems to work around this problem.
Seems that is not causing other problems, but will keep my fingers crossed.

Regards,
#991550#10
Date:
2021-08-02 22:26:04 UTC
From:
To:
El mar, 27 jul 2021 a las 11:56, Agustin Martin
(<agmartin@debian.org>) escribió:
...

Just to clarify that this was added to my custom service. Fortunately
this problem seems to only affect custom services (do not know why)
and not always.

Regards,