Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMichal Sekletar
2022-01-03 11:26:30 UTC
Description of problem:
When we enter rate-limited state we completely disregard /proc/self/mountinfo notifications for some time. If during that time, some mount unit is active (mounted) and the unit gets unmounted manually systemd will still track its state as active (mounted). Subsequent Start() operation on such unit will be effectively NOP. After leaving rate-limited state we will have inconsistency. Mount is unmounted, but systemd will still considered unit as active (mounted).
Version-Release number of selected component (if applicable):
systemd-239-54.el8.x86_64
How reproducible:
deterministic
Steps to Reproduce:
echo 'tmpfs /mnt tmpfs defaults,nofail 0 0' >> /etc/fstab
systemctl daemon-reload
mkdir -p foo
systemctl start mnt.mount
for ((i=0;i<50;++i)); do mount --bind foo foo; umount foo; done;
umount /mnt; systemctl start mnt.mount; echo $?; mountpoint /mnt; systemctl status mnt.mount; mountpoint /mnt
Actual results:
0
/mnt is not a mountpoint
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; generated)
Active: active (mounted) since Mon 2022-01-03 05:22:08 EST; 54min ago
Where: /mnt
What: tmpfs
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Tasks: 0 (limit: 11356)
Memory: 4.0K
CGroup: /system.slice/mnt.mount
Jan 03 05:22:08 ci-vm-10-0-136-183.hosted.upshift.rdu2.redhat.com systemd[1]: mnt.mount: Directory /mnt to mount over is not empty, mounting anyway.
Jan 03 05:22:08 ci-vm-10-0-136-183.hosted.upshift.rdu2.redhat.com systemd[1]: Mounting /mnt...
Jan 03 05:22:08 ci-vm-10-0-136-183.hosted.upshift.rdu2.redhat.com systemd[1]: Mounted /mnt.
/mnt is not a mountpoint
Expected results:
/mnt is mounted as a result of systemctl start mnt.mount.
Additional info:
https://github.com/systemd/systemd/issues/20329
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2069
Description of problem: When we enter rate-limited state we completely disregard /proc/self/mountinfo notifications for some time. If during that time, some mount unit is active (mounted) and the unit gets unmounted manually systemd will still track its state as active (mounted). Subsequent Start() operation on such unit will be effectively NOP. After leaving rate-limited state we will have inconsistency. Mount is unmounted, but systemd will still considered unit as active (mounted). Version-Release number of selected component (if applicable): systemd-239-54.el8.x86_64 How reproducible: deterministic Steps to Reproduce: echo 'tmpfs /mnt tmpfs defaults,nofail 0 0' >> /etc/fstab systemctl daemon-reload mkdir -p foo systemctl start mnt.mount for ((i=0;i<50;++i)); do mount --bind foo foo; umount foo; done; umount /mnt; systemctl start mnt.mount; echo $?; mountpoint /mnt; systemctl status mnt.mount; mountpoint /mnt Actual results: 0 /mnt is not a mountpoint ● mnt.mount - /mnt Loaded: loaded (/etc/fstab; generated) Active: active (mounted) since Mon 2022-01-03 05:22:08 EST; 54min ago Where: /mnt What: tmpfs Docs: man:fstab(5) man:systemd-fstab-generator(8) Tasks: 0 (limit: 11356) Memory: 4.0K CGroup: /system.slice/mnt.mount Jan 03 05:22:08 ci-vm-10-0-136-183.hosted.upshift.rdu2.redhat.com systemd[1]: mnt.mount: Directory /mnt to mount over is not empty, mounting anyway. Jan 03 05:22:08 ci-vm-10-0-136-183.hosted.upshift.rdu2.redhat.com systemd[1]: Mounting /mnt... Jan 03 05:22:08 ci-vm-10-0-136-183.hosted.upshift.rdu2.redhat.com systemd[1]: Mounted /mnt. /mnt is not a mountpoint Expected results: /mnt is mounted as a result of systemctl start mnt.mount. Additional info: https://github.com/systemd/systemd/issues/20329