[opensuse] I mount a disk and systemd umounts it automatically and instantly
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Telcontar:/data # mount -v /data/storage_e mount: /dev/mapper/cr_storage_e mounted on /data/storage_e. Telcontar:/data # mount | grep /data/storage_e Telcontar:/data # Telcontar:/data # systemctl status data-storage_e.mount data-storage_e.mount - /data/storage_e Loaded: loaded (/etc/fstab) Active: inactive (dead) Where: /data/storage_e What: /dev/disk/by-label/e_storage Jun 29 13:27:46 Telcontar systemd[1]: Unmounted /data/storage_e. Jun 29 13:28:56 Telcontar systemd[1]: Unit data-storage_e.mount is bound to inactive service. Stopping, too. Jun 29 13:28:56 Telcontar systemd[1]: Unmounting /data/storage_e... Jun 29 13:28:56 Telcontar systemd[1]: Unmounted /data/storage_e. Jun 29 13:29:02 Telcontar systemd[1]: Unit data-storage_e.mount is bound to inactive service. Stopping, too. Jun 29 13:29:02 Telcontar systemd[1]: Unmounting /data/storage_e... Jun 29 13:29:02 Telcontar systemd[1]: Unmounted /data/storage_e. Jun 29 13:30:06 Telcontar systemd[1]: Unit data-storage_e.mount is bound to inactive service. Stopping, too. Jun 29 13:30:06 Telcontar systemd[1]: Unmounting /data/storage_e... Jun 29 13:30:06 Telcontar systemd[1]: Unmounted /data/storage_e. Telcontar:/data # <0.5> 2016-06-29 13:30:06 Telcontar kernel - - - [1052825.043293] XFS (dm-2): Mounting V4 Filesystem <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** /proc/self/mountinfo changed <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** MOUNTED /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGING /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** UPDATING /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** EMITTING CHANGED for /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGED /sys/devices/virtual/block/dm-2 <0.6> 2016-06-29 13:30:06 Telcontar kernel - - - [1052825.139471] XFS (dm-2): Ending clean mount <3.6> 2016-06-29 13:30:06 Telcontar systemd 1 - - Unit data-storage_e.mount is bound to inactive service. Stopping, too. <3.6> 2016-06-29 13:30:06 Telcontar systemd 1 - - Unmounting /data/storage_e... <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** /proc/self/mountinfo changed <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** UNMOUNTED /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGING /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** UPDATING /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** EMITTING CHANGED for /sys/devices/virtual/block/dm-2 <1.6> 2016-06-29 13:30:06 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGED /sys/devices/virtual/block/dm-2 <3.6> 2016-06-29 13:30:06 Telcontar systemd 1 - - Unmounted /data/storage_e. fstab: /dev/mapper/cr_storage_e /data/storage_e xfs nofail,relatime,noauto 1 5 How can I stop systemd from undoing what I do? I certainly want to mount that disk! - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAldzsyoACgkQtTMYHG2NR9XCaQCcCjiPuIAmOkGptfWUdjE6KwQ5 W4UAnRNbiTOpPyEd+pZGUivClZSDmGbs =KWGh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jun 29, 2016 at 2:38 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Unit data-storage_e.mount is bound to inactive service.
Welcome to the hell^Wclub. This commit was supposed to fix it: https://cgit.freedesktop.org/systemd/systemd/commit/src/core/mount.c?id=628c... so you should open bug report and quote it. Although in this case the first question is why /dev/mapper/cr_storage_e is considered inactive if device obviously exists. So more details are required. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-29 13:47, Andrei Borzenkov wrote:
On Wed, Jun 29, 2016 at 2:38 PM, Carlos E. R. <> wrote:
Unit data-storage_e.mount is bound to inactive service.
Welcome to the hell^Wclub. This commit was supposed to fix it:
https://cgit.freedesktop.org/systemd/systemd/commit/src/core/mount.c?id=628c...
so you should open bug report and quote it. Although in this case the first question is why /dev/mapper/cr_storage_e is considered inactive if device obviously exists. So more details are required.
What details? Report against what? Systemd people will ignore it, as they ignored other reports I made for new bugs after updates, because this is 13.1. Well, I changed the mount point to "/data/test" and it mounted instantly, and is still there. I can ignore the issue for now. :-} -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wednesday 29 June 2016, Carlos E. R. wrote:
On 2016-06-29 13:47, Andrei Borzenkov wrote:
On Wed, Jun 29, 2016 at 2:38 PM, Carlos E. R. <> wrote:
Unit data-storage_e.mount is bound to inactive service.
Welcome to the hell^Wclub. This commit was supposed to fix it:
https://cgit.freedesktop.org/systemd/systemd/commit/src/core/mount. c?id=628c89cc68ab96fce2de7ebba5933725d147aecc
so you should open bug report and quote it. Although in this case the first question is why /dev/mapper/cr_storage_e is considered inactive if device obviously exists. So more details are required.
What details?
Report against what? Systemd people will ignore it, as they ignored other reports I made for new bugs after updates, because this is 13.1.
Is the patch above already in the systemd version you are using?
Well, I changed the mount point to "/data/test" and it mounted instantly, and is still there. I can ignore the issue for now. :-} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-29 14:00, Ruediger Meier wrote:
On Wednesday 29 June 2016, Carlos E. R. wrote:
On 2016-06-29 13:47, Andrei Borzenkov wrote:
On Wed, Jun 29, 2016 at 2:38 PM, Carlos E. R. <> wrote:
Unit data-storage_e.mount is bound to inactive service.
Welcome to the hell^Wclub. This commit was supposed to fix it:
https://cgit.freedesktop.org/systemd/systemd/commit/src/core/mount.c?id=628c...
so you should open bug report and quote it. Although in this case the first question is why /dev/mapper/cr_storage_e is considered inactive if device obviously exists. So more details are required.
What details?
Report against what? Systemd people will ignore it, as they ignored other reports I made for new bugs after updates, because this is 13.1.
Is the patch above already in the systemd version you are using?
I don't know how to find out. Let me see. I have systemd-210-46.1.x86_64 Telcontar:/data # rpm -q --changelog systemd | grep "core: rework" Telcontar:/data # Telcontar:/data # rpm -q --changelog systemd | grep core | grep rework 0001-core-rework-device-state-logic.patch Telcontar:/data # Maybe yes. It would be "core: rework device state logic" * Fri Mar 13 2015 werner@suse.de - Add upstream patch 0001-core-rework-device-state-logic.patch to fix a reace condition where systemd unmounts devices known by the sysfs but not by udev (bsc#921898) So yes, I understand it was added long ago. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/29/2016 02:29 PM, Carlos E. R. wrote:
I don't know how to find out. Let me see.
I have systemd-210-46.1.x86_64
Telcontar:/data # rpm -q --changelog systemd | grep "core: rework" Telcontar:/data # Telcontar:/data # rpm -q --changelog systemd | grep core | grep rework 0001-core-rework-device-state-logic.patch Telcontar:/data #
Maybe yes. It would be "core: rework device state logic"
* Fri Mar 13 2015 werner@suse.de - Add upstream patch 0001-core-rework-device-state-logic.patch to fix a reace condition where systemd unmounts devices known by the sysfs but not by udev (bsc#921898)
So yes, I understand it was added long ago.
That's one of the challenges with SuSE's use of systemd, the version used is well behind the upstream release (and probably why the bugs are ignored by freedesktop folks) Current version (as of update a few days ago on a Arch box) is systemd 230-4. It not a bad thing, it is a "challenging" thing that can lead to strange behavior. Hopefully they will get it patched in a way that works for you. On 13.1, thankfully, I have had no issues (but it's partially because I've only had a single drive). - -- David C. Rankin, J.D.,P.E. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAld0UbsACgkQZMpuZ8CyrcigNQCdHEecM1Ez235u7y3nJCSQsFD9 EC8Ani4b5DTibDo+LbkNi2Xmtn48Y03I =8tvx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-30 00:54, David C. Rankin wrote:
That's one of the challenges with SuSE's use of systemd, the version used is well behind the upstream release (and probably why the bugs are ignored by freedesktop folks) Current version (as of update a few days ago on a Arch box) is systemd 230-4.
It is expected that 13.1 has an old release. Only TW can be expected to have a recent version. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-06-29 13:38, Carlos E. R. wrote: Full log: <5>1 2016-06-29T13:45:33.794545+02:00 Telcontar kernel - - - [1053752.288904] XFS (dm-2): Mounting V4 Filesystem <6>1 2016-06-29T13:45:33.888909+02:00 Telcontar kernel - - - [1053752.377306] XFS (dm-2): Ending clean mount <30>1 2016-06-29T13:45:33.891626+02:00 Telcontar systemd 1 - - Unit data-storage_e.mount is bound to inactive service. Stopping, too. <30>1 2016-06-29T13:45:33.892625+02:00 Telcontar systemd 1 - - Unmounting /data/storage_e... <14>1 2016-06-29T13:45:33.892800+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** /proc/self/mountinfo changed <14>1 2016-06-29T13:45:33.892978+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** MOUNTED /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.893135+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGING /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.893290+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** UPDATING /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.893447+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** EMITTING CHANGED for /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.893607+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGED /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.897421+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** /proc/self/mountinfo changed <14>1 2016-06-29T13:45:33.897627+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** UNMOUNTED /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.897787+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGING /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.897941+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** UPDATING /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.898096+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** EMITTING CHANGED for /sys/devices/virtual/block/dm-2 <14>1 2016-06-29T13:45:33.898251+02:00 Telcontar org.freedesktop.UDisks 1154 - - **** CHANGED /sys/devices/virtual/block/dm-2 <30>1 2016-06-29T13:45:33.968572+02:00 Telcontar systemd 1 - - Unmounted /data/storage_e. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wednesday 29 June 2016, Carlos E. R. wrote:
How can I stop systemd from undoing what I do? I certainly want to mount that disk!
This happens also the other way around. Systemd mount's devices again after you umounted them manually. I wonder if it's possible to configure systemd to neither mount nor umount anything. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-29 13:58, Ruediger Meier wrote:
On Wednesday 29 June 2016, Carlos E. R. wrote:
How can I stop systemd from undoing what I do? I certainly want to mount that disk!
This happens also the other way around. Systemd mount's devices again after you umounted them manually. I wonder if it's possible to configure systemd to neither mount nor umount anything.
True. I prevent that by saying in fstab "noauto". -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E. R. -
David C. Rankin -
Ruediger Meier