Bug 1653207

Summary:	systemd-fstab-generator: the device listed in /etc/fstab is removed automatically when executing "systemctl start mount_point"
Product:	Red Hat Enterprise Linux 8	Reporter:	Yongcheng Yang <yoyang>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	qe-baseos-daemons
Severity:	high	Docs Contact:
Priority:	high
Version:	8.0	CC:	systemd-maint-list, xzhou
Target Milestone:	rc	Keywords:	Reproducer
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-29 10:53:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 2 Yongcheng Yang 2019-08-29 10:53:31 UTC

This problem has been resolved ready. But I'm not sure which is the exact version.
Just closing it now.

[root@ ]# ./bz1653207.sh 
$ tail -2 /etc/fstab
/tmp/test_img.xfs  /export_test.xfs  xfs  auto  0 0
/tmp/test_img.ext4  /export_test.ext4  ext4  auto  0 0
$ ls -l /tmp/test_img.*
-rw-r--r--. 1 root root 1073741824 Aug 29 06:51 /tmp/test_img.ext4
-rw-r--r--. 1 root root 1073741824 Aug 29 06:51 /tmp/test_img.xfs
$ systemctl start /export_test.xfs
/export_test.xfs is a mountpoint
$ systemctl start /export_test.ext4
/export_test.ext4 is a mountpoint
[root@ ]# rpm -q systemd
systemd-239-17.el8.x86_64

Comment 3 Yongcheng Yang 2019-09-04 09:35:16 UTC

(In reply to Yongcheng Yang from comment #2)
> This problem has been resolved ready. But I'm not sure which is the exact

The root cause is that tmp.mount may be started and /tmp over-mounted as a result.

And after that, same reproducer cannot trigger the failure. Than's why I thought it fixed before.

*** This bug has been marked as a duplicate of bug 1748840 ***