Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25502 - [filesystem] 2011.08-1 and /tmp

Attached to Project: Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Wednesday, 10 August 2011, 23:35 GMT
Last edited by Tom Gundersen (tomegun) - Thursday, 11 August 2011, 10:32 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

in this release /tmp is mounted as tmpfs.
After upgrading from previous release, and rebooting, /tmp is mounted as tmpfs before old /tmp folder is cleaned. This means the /tmp/temporaryfiles from old session are still there.
Now type init s and umount /tmp and you will find the old /tmp/temporaryfiles.
They can now be manually removed then /tmp mounted again and problem is solved.
But if the user neglects to do this, then this is temporary data that is stuck on the disk forever.

I'm not sure what workaround can be done. Perhaps a post install message can be added?
This task depends upon

Closed by  Tom Gundersen (tomegun)
Thursday, 11 August 2011, 10:32 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Probably better on a wiki or something like that.
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 11 August 2011, 01:10 GMT
Is not needed to go single user. If /tmp is not used just unmount it (or move), otherwise mount where /tmp reside on any place and delete files on it.
Comment by Tom Gundersen (tomegun) - Thursday, 11 August 2011, 10:03 GMT
@hussam: thanks for taking the time to report.

However, I am inclined to leave this as it is. The main reason is that we want to minimize the number of install messages, if we have too many, we risk important messages getting lost.

The reason I think this is ok not to notify about is: the potential problem (lost space) is pretty minor. Furthermore, it is only a problem on existing systems, and on existing systems the change is not made automatically. The user has to manually merge the new fstab (or they could choose not to, if they prefer). I think it is expected that an Arch user knows that if mounting on a directory does not delete any existing files, so it should be clear what happens.

Maybe your (or djgera's) guide to how to solve the problem would be nice on the wiki?
Comment by Hussam Al-Tayeb (hussam) - Thursday, 11 August 2011, 10:11 GMT
Yes, the first thing that crossed my mind when merging the new fstab was old files /tmp and I agree that ArchLinux users should be able to notice that too. You can close the bug report now if you'd like. Thank you for the comments :)

Loading...