![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
-----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