After updating I found a path /run/run which cannot be right can it ? I was unsure if I should have posted this under developers, but I thought this was more fitting.
# mount | grep loop
/dev/loop0p1 on /media/test/kernel type ext4 (ro,nosuid,nodev,relatime,uhelper=udisks2)
/dev/loop0p2 on /media/test/disk type squashfs (ro,nosuid,nodev,relatime,errors=continue,uhelper=udisks2)
# cd disk
# find ./run -exec ls -ld {} \;
drwxr-xr-x 3 root root 26 Nov 28 22:33 ./run
drwxr-xr-x 2 root root 30 Nov 28 22:33 ./run/apk
-rw------- 1 root root 0 Nov 28 22:33 ./run/apk/db.lock
# mount | grep loop
/dev/loop0p1 on /media/test/kernel type ext4 (ro,nosuid,nodev,relatime,uhelper=udisks2)
/dev/loop0p2 on /media/test/disk type squashfs (ro,nosuid,nodev,relatime,errors=continue,uhelper=udisks2)
# cd disk
# find ./run -exec ls -ld {} \;
drwxr-xr-x 3 root root 26 Nov 21 22:04 ./run
drwxr-xr-x 2 root root 30 Nov 21 22:04 ./run/apk
-rw------- 1 root root 0 Nov 21 22:04 ./run/apk/db.lock
# mount | grep loop
/dev/loop0p1 on /media/test/kernel type ext4 (ro,nosuid,nodev,relatime,uhelper=udisks2)
/dev/loop0p2 on /media/test/disk type squashfs (ro,nosuid,nodev,relatime,errors=continue,uhelper=udisks2)
# cd disk
# find ./run -exec ls -ld {} \;
find: ‘./run’: No such file or directory
I made a mistake in post8, the commit window is between 1st-24th.
Noted.
Correct me if I'm wrong, but the lock file is generated to ensure only one instance is running and is cleaned up after. Assuming it cannot be removed during, I suspect some process kept it open and cleanup fails.