# modprobe brd
# mkfs.xfs /dev/ram0
# mount /dev/ram0 /mnt/
# umount /mnt
umount: /mnt/: not mounted
The device mounts initially and then very shortly thereafter is unmounted by systemd with the following in the logs:
localhost systemd: Unit mnt.mount is bound to inactive unit. Stopping, too.
localhost systemd: Unmounting /mnt...
localhost systemd: Unmounted /mnt.
localhost systemd: Unit mnt.mount entered failed state.
This problem occurs with systemd-219-4.fc22.x86_64. It did not occur with systemd-318-*. The kernel is 4.0.0-0.rc1.git0.1.fc22.x86_64.
Fixed in git.
systemd-219-9.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-219-9.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
systemd-219-9.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Is this bug really fixed in systemd-219-9.fc22? I have just seen it in the current F21 version and wanted to see the fix, but I can't find it in neither the upstream repo nor the fedora repo. Zbyszek, could you please point me to the patch?
See commits 496068a82, 628c89c.
I thought that this bug appeared only recently. If we have the same thing in F21, then maybe you can open a separate bug so we can track it more easily?