Hi guys!
I reported a strange bug in which a user cannot unmount an USB device if it is not in /etc/fstab. Well, it became very strange when I saw that if I install openSUSE Tumbleweed from the GNOME LiveCD then I **do not** have the problem, whereas the problem occurs if I install from the standard DVD.
After a careful digging, it turns out that the problem is caused because /var/run is not a symlink to /run when I install Tumbleweed from the standard DVD. When the installation is done from the GNOME LiveCD, then /var/run is indeed a symlink to /run and the problem does not occur.
Hence, my question is: must /var/run always be a symlink to /run ? If so, I think we need to open a bug against openSUSE installation software.
Notice that I could fix the problem when I enter in the system in maintenance mode, unmount /var/run, deleted it, and then symlink /run to /var/run.
Best regards, Ronan Arraes
Hello,
Am 6. Oktober 2016, 09:49:18 CEST schrieb Ronan Arraes Jardim Chagas:
I reported a strange bug in which a user cannot unmount an USB device if it is not in /etc/fstab. Well, it became very strange when I saw that if I install openSUSE Tumbleweed from the GNOME LiveCD then I **do not** have the problem, whereas the problem occurs if I install from the standard DVD.
After a careful digging, it turns out that the problem is caused because /var/run is not a symlink to /run when I install Tumbleweed from the standard DVD. When the installation is done from the GNOME LiveCD, then /var/run is indeed a symlink to /run and the problem does not occur.
That sounds interesting[tm].
Hence, my question is: must /var/run always be a symlink to /run ? If so, I think we need to open a bug against openSUSE installation software.
To make things even more interesting:
# ls -ld /var/run drwxr-xr-x 43 root root 1220 6. Okt 17:53 /var/run/ # rpm -qf /var/run filesystem-13.3-10.2.x86_64 # rpm -qlv filesystem | grep /var/run lrwxrwxrwx 1 root root 4 Jun 15 14:20 /var/run -> /run
This means the "filesystem" package ships it as symlink, but for some reason it gets created as real directory. Either this gets done by the installer, or something needs /var/run/ before the filesystem package gets installed. Both don't sound too likely, but it's probably one of these.
So - yes, please open a bugreport and report back the bugzilla link here. (I'd like to watch that bugreport.)
Regards,
Christian Boltz
On Thursday 2016-10-06 22:54, Christian Boltz wrote:
# ls -ld /var/run drwxr-xr-x 43 root root 1220 6. Okt 17:53 /var/run/ # rpm -qf /var/run filesystem-13.3-10.2.x86_64 # rpm -qlv filesystem | grep /var/run lrwxrwxrwx 1 root root 4 Jun 15 14:20 /var/run -> /run
This means the "filesystem" package ships it as symlink, but for some reason it gets created as real directory.
Last time I checked, rpm does not replace directories with non-directories. (And there is/was special logic - %post? - in some package to pull it off "manually".)
The only conceivable setting where this might have happened is that an update from an earlier openSUSE when it moved from /var/run to /run did not go as planned.
On 10/06/2016 10:54 PM, Christian Boltz wrote:
To make things even more interesting:
# ls -ld /var/run drwxr-xr-x 43 root root 1220 6. Okt 17:53 /var/run/ # rpm -qf /var/run filesystem-13.3-10.2.x86_64 # rpm -qlv filesystem | grep /var/run lrwxrwxrwx 1 root root 4 Jun 15 14:20 /var/run -> /run
This means the "filesystem" package ships it as symlink, but for some reason it gets created as real directory. Either this gets done by the installer, or something needs /var/run/ before the filesystem package gets installed. Both don't sound too likely, but it's probably one of these.
Isn't /var/run expected to be a bind-mount to /run on some systems? I thought I've seen that somewhere ... therefore, a directory would be fine ...
Have a nice day, Berny
Hi,
Em qui, 2016-10-06 às 22:54 +0200, Christian Boltz escreveu:
So - yes, please open a bugreport and report back the bugzilla link here. (I'd like to watch that bugreport.)
Well, there is a bug report for the original problem (user being not able to unmount a USB device in GNOME). I think we should use it, maybe change the title?
https://bugzilla.opensuse.org/show_bug.cgi?id=1001554
Best regards, Ronan Arraes
Hi,
Em qui, 2016-10-06 às 23:01 +0200, Jan Engelhardt escreveu:
The only conceivable setting where this might have happened is that an update from an earlier openSUSE when it moved from /var/run to /run did not go as planned.
Actually, it is happening to a new installation using the latest DVD ISO. Notice that if I install using GNOME LiveCD, for example, then /var/run is a symlink to /run and everything works fine. Hence, something is happening to the standard DVD installation that is creating /var/run directory.
Best regards, Ronan Arraes
Op vrijdag 7 oktober 2016 04:33:21 CEST schreef Ronan Arraes Jardim Chagas:
Hi,
Em qui, 2016-10-06 às 23:01 +0200, Jan Engelhardt escreveu:
The only conceivable setting where this might have happened is that an update from an earlier openSUSE when it moved from /var/run to /run did not go as planned.
Actually, it is happening to a new installation using the latest DVD ISO. Notice that if I install using GNOME LiveCD, for example, then /var/run is a symlink to /run and everything works fine. Hence, something is happening to the standard DVD installation that is creating /var/run directory.
Best regards, Ronan Arraes
I can confirm this.
On 2016-10-07 13:17, Knurpht - Gertjan Lettink wrote:
Op vrijdag 7 oktober 2016 04:33:21 CEST schreef Ronan Arraes Jardim Chagas:
Hi,
Em qui, 2016-10-06 às 23:01 +0200, Jan Engelhardt escreveu:
The only conceivable setting where this might have happened is that an update from an earlier openSUSE when it moved from /var/run to /run did not go as planned.
Actually, it is happening to a new installation using the latest DVD ISO. Notice that if I install using GNOME LiveCD, for example, then /var/run is a symlink to /run and everything works fine. Hence, something is happening to the standard DVD installation that is creating /var/run directory.
Best regards, Ronan Arraes
I can confirm this.
I notice this:
System A (installed fresh as Beta 1 DVD, then upgraded to 2 and 3):
linux-qyxj:~ # mount | grep tmpfs devtmpfs on /dev type devtmpfs (rw,nosuid,size=360232k,nr_inodes=90058,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) tmpfs on /run/user/482 type tmpfs (rw,nosuid,nodev,relatime,size=73288k,mode=700,uid=482,gid=483) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=73288k,mode=700,uid=1000,gid=100) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=73288k,mode=700) linux-qyxj:~ #
linux-qyxj:~ # l /var total 52 drwxr-xr-x 12 root root 4096 Aug 31 15:28 ./ drwxr-xr-x 23 root root 4096 Sep 22 14:18 ../ ... lrwxrwxrwx 1 root root 9 Aug 31 15:02 lock -> /run/lock/ ... lrwxrwxrwx 1 root root 10 Aug 31 15:02 mail -> spool/mail/ ... lrwxrwxrwx 1 root root 4 Aug 31 15:02 run -> /run/ ... linux-qyxj:~ #
System B (upgraded from 13.1 using DVD):
Eleanor4-up:~ # mount | grep tmpfs devtmpfs on /dev type devtmpfs (rw,nosuid,size=361796k,nr_inodes=90449,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,mode=755) <================ tmpfs on /var/run type tmpfs (rw,nosuid,nodev,mode=755) <================= tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=74544k,mode=700) tmpfs on /var/run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=74544k,mode=700) Eleanor4-up:~ #
Hi,
# ll -i /var | grep run; echo; ll -i / | grep run 916368 lrwxrwxrwx 1 root root 9 вер 11 04:34 lock -> /run/lock 12033 drwxr-xr-x 34 root root 900 жов 10 14:42 run
12033 drwxr-xr-x 34 root root 900 жов 10 14:42 run
It look like they are hard-linked on my system.
неділя, 9 жовтня 2016 р. 02:15:36 EEST Carlos E. R. написано:
On 2016-10-07 13:17, Knurpht - Gertjan Lettink wrote:
Op vrijdag 7 oktober 2016 04:33:21 CEST schreef Ronan Arraes Jardim
Chagas:
Hi,
Em qui, 2016-10-06 às 23:01 +0200, Jan Engelhardt escreveu:
The only conceivable setting where this might have happened is that an update from an earlier openSUSE when it moved from /var/run to /run did not go as planned.
Actually, it is happening to a new installation using the latest DVD ISO. Notice that if I install using GNOME LiveCD, for example, then /var/run is a symlink to /run and everything works fine. Hence, something is happening to the standard DVD installation that is creating /var/run directory.
Best regards, Ronan Arraes
I can confirm this.
I notice this:
System A (installed fresh as Beta 1 DVD, then upgraded to 2 and 3):
linux-qyxj:~ # mount | grep tmpfs devtmpfs on /dev type devtmpfs (rw,nosuid,size=360232k,nr_inodes=90058,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) tmpfs on /run/user/482 type tmpfs (rw,nosuid,nodev,relatime,size=73288k,mode=700,uid=482,gid=483) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=73288k,mode=700,uid=1000,gid=100) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=73288k,mode=700) linux-qyxj:~ #
linux-qyxj:~ # l /var total 52 drwxr-xr-x 12 root root 4096 Aug 31 15:28 ./ drwxr-xr-x 23 root root 4096 Sep 22 14:18 ../ ... lrwxrwxrwx 1 root root 9 Aug 31 15:02 lock -> /run/lock/ ... lrwxrwxrwx 1 root root 10 Aug 31 15:02 mail -> spool/mail/ ... lrwxrwxrwx 1 root root 4 Aug 31 15:02 run -> /run/ ... linux-qyxj:~ #
System B (upgraded from 13.1 using DVD):
Eleanor4-up:~ # mount | grep tmpfs devtmpfs on /dev type devtmpfs (rw,nosuid,size=361796k,nr_inodes=90449,mode=755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,mode=755) <================ tmpfs on /var/run type tmpfs (rw,nosuid,nodev,mode=755) <================= tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=74544k,mode=700) tmpfs on /var/run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=74544k,mode=700) Eleanor4-up:~ #
10.10.2016 18:48, Mykola Krachkovsky пишет:
Hi,
# ll -i /var | grep run; echo; ll -i / | grep run 916368 lrwxrwxrwx 1 root root 9 вер 11 04:34 lock -> /run/lock 12033 drwxr-xr-x 34 root root 900 жов 10 14:42 run
12033 drwxr-xr-x 34 root root 900 жов 10 14:42 run
It look like they are hard-linked on my system.
No, they are bind-mounted.
-
Andrei Borzenkov -
Bernhard Voelker -
Carlos E. R. -
Christian Boltz -
Jan Engelhardt -
Knurpht - Gertjan Lettink -
Mykola Krachkovsky -
Ronan Arraes Jardim Chagas