- Status Unconfirmed
- Percent Complete
- Task Type Bug Report
- Category Base system
- Assigned To No-one
- Operating System All
- Severity Medium
- Priority Very Low
- Reported Version Trunk
- Due in Version Undecided
-
Due Date
Undecided
- Private
FS#2057 - /etc/init.d/umount runs after other block devices must stop
Supply the following if possible:
- Device problem occurs on
All.
- Software versions of OpenWrt/LEDE release, packages, etc.
18.06.01 & snapshots
- Steps to reproduce
Setup another block device that should be stopped after umount, e.g. cryptsetup, lvm2, or mdadm
Performing umount as K99umount allows very few things to run afterwards. Ideally, it would be K96umount or K97umount, which would allow for running multiple levels of stops afterwards. There should be at least two levels after umount.
For example, setting K98umount would still cause problems for K99cryptsetup & K99lvm2 because lvm2 must stop before cryptsetup and both must stop after mount.
Changing S99umount may also affect these other packages:
STOP=98 boot
STOP=98 kdump.init
STOP=98 mdadm.init
STOP=99 conserver.init
STOP=99 kismet_drone.init
STOP=99 kismet_server.init
STOP=99 socat.init