Bugzilla – Bug 1017683
/var/run should not be separate filesystem from /run
Last modified: 2017-01-09 11:04:19 UTC
Tumbleweed installation allows (like all other Suse versions) to create /tmp, /run, /var/lock and /var/run as separate tmpfs filesystems. Recently (sometime on last November) Tumbleweed behaviour changed so that many things don't work or are very slow, if /run and /var/run are separate. See <https://forums.opensuse.org/showthread.php/521509-X-broke-gt-after-new-intall-KDE-is-slow> for more info. Solution for experienced problems was to remove entry for /var/run from /etc/fstab and leave bind mounting /var/run to /run for systemd boot process. If using btrfs, there is no sense creating /var/run as subvolume, as it either is not used (overridden by bind mount) or it hides bind mount causing all sorts of problems described of which some were described in separate forum post, see link above.
Stefan, what's your POV about this? Thanks in advance!
The current list of subvolumes was requested by product management. I have no strong feelings about removing or adding yet another one. Furthermore, they are now configurable in control.xml, so it's up to the project/product/release manager of each product how to handle this. But the root of the problem appears to be somewhere else, so IMHO it's not really useful to micro-optimize the symptom. But that is beyond the scope of YaST.
AFAIS the reporter wants to disallow users to create filesystems in the expert partitioner with certain mount-points, e.g. /var/run. Please make a feature requets for that (fate.opensuse.org).