If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
openSUSE:Tmp on tmpfs
tmpfs is a temporary filesystem that resides in memory. Mounting directories as tmpfs can be an effective way of speeding up accesses to their files and to ensure that their contents are automatically cleared upon reboot. This makes it a logical choice for some mountpoint such as `/tmp`
It was decided to mount `/tmp` as tmpfs after a discussion on the opensuse-factory mailing list starting at:
Since Snapshot Version 20200806 fresh installations will will use tmpfs for /tmp by default. Existing systems will not be changed.
Converting old installations to use tmpfs
- Backup any files you wish to keep from /tmp
- Remove the line for /tmp from /etc/fstab
- Remove all files in /tmp
Old Installations already using /tmp on tmpfs before Snapshot 20200806
Before Snapshot 20200806, some users may have taken the steps to use the systemd-provided tmp.mount unit which had been relocated to /usr/share/systemd/tmp.mount. This most likely would have been in the form of one of the following two steps
- running "systemctl link /usr/share/systemd/tmp.mount"
- copying /usr/share/systemd/tmp.mount to /etc/systemd/system
For either scenario you first need to ensure you do not have any entry in /etc/fstab for for /tmp. If you do, remove it.
Then in the case of #1 you will NEED to remove /etc/systemd/system/tmp.mount to ensure you're using the new mount unit introduced as part of making /tmp on tmpfs default.
In the case of #2 it is not mandatory to remove /etc/systemd/system/tmp.mount but would be recommended to ensure you keep using the latest settings for /tmp on tmpfs in the event of any future updates changing our recommended settings.
Using disk space for /tmp
If you do not wish to use tmpfs for tmp, you need to just define a mount point for it in /etc/fstab. Then tmpfs will no longer be used for /tmp.
This is easiest with btrfs and creating a subvolume, using the "mksubvolume /tmp" command.
Alternatively, you can mask the /tmp mount point with "systemctl mask tmp.mount". NOTE: If you only mask tmp.mount while using btrfs you will be filling up your root filesystem AND creating snapshots containing the contents of tmp (in other words, don't do this, and define a subvolume)
After the next reboot all files written to /tmp are stored again on the disk and will survive future reboots.