FS#44188 - [systemd] mount broken with systemd-219
Attached to Project:
Arch Linux
Opened by John (gee) - Sunday, 15 March 2015, 08:52 GMT
Last edited by Dave Reisner (falconindy) - Monday, 16 March 2015, 13:41 GMT
Opened by John (gee) - Sunday, 15 March 2015, 08:52 GMT
Last edited by Dave Reisner (falconindy) - Monday, 16 March 2015, 13:41 GMT
|
Details
Description:
With systemd-219 (-2 and -3, I did not try with -1), I can mount an iso once, unmount it but after that I can never mount something again till next reboot. dmesg shows nothing, and mount doesn't error. But systemctl shows that the mount happened, and then right away was unmounted. This is pretty much this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1196452 which is mentioned as fixed in git, but since it doesn't mention the commit, I don't know. Steps to reproduce: 1) Use systemd-219 from testing 2) Mount an image (it might work with a real device, I have not tried) 3) Unmount it 4) Try to mount it again 5) look at the mounted folder's content, nothing should be there (or the old content before the mount happened). Rolling back to the core repo build works fine. Thanks! |
This task depends upon
Closed by Dave Reisner (falconindy)
Monday, 16 March 2015, 13:41 GMT
Reason for closing: Won't fix
Additional comments about closing: I'm not backporting this -- the fix will be available with v220.
Monday, 16 March 2015, 13:41 GMT
Reason for closing: Won't fix
Additional comments about closing: I'm not backporting this -- the fix will be available with v220.
If a backport doesn't make sense, would it be ok to use Fedora's source?
This build, mentioned in the bug:
https://admin.fedoraproject.org/updates/systemd-219-9.fc22
includes the fix
If not, I can stick to 218 till 220 comes out, in probably a month, it is not a blocker to me.
But it took me quite some time to figure it out, I just hope that no one else loses time over this...
http://cgit.freedesktop.org/systemd/systemd/commit/?id=496068a82880