Bug ID 1181066
Summary YaST mounts target /run on top of running system
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component YaST2
Assignee yast2-maintainers@suse.de
Reporter fvogt@suse.com
QA Contact jsrain@suse.com
Found By ---
Blocker ---

I noticed that while YaST runs, (/mnt)/run of the target system is bind mounted
on top of /run.
This impacts the live environment badly, as it's pretty much unusuable without
dbus and wayland sockets and so on...

/proc/self/mountinfo shows:

644 577 0:24 / /mnt/run rw,nosuid,nodev shared:24 - tmpfs tmpfs
rw,size=802844k,nr_inodes=819200,mode=755,inode64
661 644 0:24 / /mnt/run rw,nosuid,nodev shared:24 - tmpfs tmpfs
rw,size=802844k,nr_inodes=819200,mode=755,inode64
662 28 0:24 / /run rw,nosuid,nodev shared:24 - tmpfs tmpfs
rw,size=802844k,nr_inodes=819200,mode=755,inode64

So it seems like YaST basically does:

mount -t tmpfs tmpfs /mnt/run
mount --bind /mnt/run /mnt/run
mount --bind /mnt/run /run

Why not just mount --bind /run /mnt/run?


You are receiving this mail because: