"block umount" unmounts "/rom/overlay". Bug?

Installing and Using OpenWrt
1

(on a fresh 23.05.2 box)

root@OpenWrt:~# mount | grep /rom/overlay
/dev/ubi0_2 on /rom/overlay type ubifs (rw,noatime,assert=read-only,ubi=0,vol=2)
root@OpenWrt:~# block umount
root@OpenWrt:~# mount | grep /rom/overlay
root@OpenWrt:~#

(NB: /etc/config/fstab is completely empty.)

Is this a bug?

2

what makes you think it's a bug?

can you kindly add the following basic information...

Please run the following commands (copy-paste the whole block) and paste the output here, using the "Preformatted text </> " button:
grafik

ubus call system board; mount
3

Because I don't expect block umount to have any effect on "pre-existing" mounts that aren't mentioned in either /etc/config/fstab (which is empty) or in the documentation.

root@OpenWrt:~# ubus call system board; mount
{
	"kernel": "5.15.137",
	"hostname": "OpenWrt",
	"system": "xRX200 rev 1.2",
	"model": "BT Home Hub 5A",
	"board_name": "bt,homehub-v5a",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.2",
		"revision": "r23630-842932a63d",
		"target": "lantiq/xrx200",
		"description": "OpenWrt 23.05.2 r23630-842932a63d"
	}
}
/dev/root on /rom type squashfs (ro,relatime,errors=continue)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/ubi0_2 on /rom/overlay type ubifs (rw,noatime,assert=read-only,ubi=0,vol=2)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
tmpfs on /dev type tmpfs (rw,nosuid,noexec,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
bpffs on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
1 Like
4

ok, now I understand why you consider it a bug...

just to understand what the command shows:

uci show | grep fstab; cat /etc/fstab

on a router I have without any drive connected it should give a situation similar to this...

uci show | grep fstab; cat /etc/fstab
ucitrack.@fstab[0]=fstab
ucitrack.@fstab[0].exec='/sbin/block mount'
# <file system> <mount point> <type> <options> <dump> <pass>
5

Mine returns exactly the same output:

root@OpenWrt:~# uci show | grep fstab; cat /etc/fstab
ucitrack.@fstab[0]=fstab
ucitrack.@fstab[0].exec='/sbin/block mount'
# <file system> <mount point> <type> <options> <dump> <pass>
root@OpenWrt:~#

Could I please ask: Do you observe the same behaviour (as documented in my first post)?

6

yes the command managed to umount
/dev/mtdblock13 (in my case)

maybe it's time to hear from people more competent than me (I assume I can still umount all the devices) try sending a private message to:

7

I'd be happy to help, but I honestly don't know if this is expected behavior or a bug. Hopefully someone else can chime in.

1 Like
8

Bug reported here.