Bug 1298109 - tmpfs is unexpectedly mounted on /tmp in rhel-7
Summary: tmpfs is unexpectedly mounted on /tmp in rhel-7
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Branislav Blaškovič
Depends On:
Blocks: 1298209 1339488
TreeView+ depends on / blocked
Reported: 2016-01-13 09:21 UTC by Mohit Agrawal
Modified: 2019-11-14 07:19 UTC (History)
8 users (show)

Fixed In Version: systemd-219-20.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1298209 (view as bug list)
Last Closed: 2016-11-04 00:50:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2121951 0 None None None 2017-01-09 04:15:46 UTC
Red Hat Product Errata RHBA-2016:2216 0 normal SHIPPED_LIVE systemd bug fix and enhancement update 2016-11-03 13:24:51 UTC

Description Mohit Agrawal 2016-01-13 09:21:22 UTC
Description of problem:
tmpfs is unexpectedly mounted on /tmp when user start any unit file that configured PrivateTmp=true

Version-Release number of selected component (if applicable):

How reproducible:
Steps to Reproduce:
1) df /tmp
 df /tmp
Filesystem                            1K-blocks     Used Available Use% Mounted on
/dev/mapper/rhel_dell--per630--2-root  52403200 19977388  32425812  39% /

2 ) systemctl status tmp.mount; 

But after start systemd-timedated it is start automatically and created mount-point.
3 ) systemctl start systemd-timedated; 
4) df /tmp
Filesystem     1K-blocks  Used Available Use% Mounted on
tmpfs            8010868     0   8010868   0% /tmp

Actual results:
/tmp is created new mount point on tmpfs

Expected results:
mount point should not create automatically.

Additional info:

Comment 3 Lukáš Nykrýn 2016-01-13 09:49:41 UTC
Just a small note, workaround for this issue is to mask the tmp.mount by calling:

systemctl mask tmp.mount

Comment 13 errata-xmlrpc 2016-11-04 00:50:26 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.