[systemd-bugs] [Bug 68232] Cleaning up of /tmp directories PrivateTmp=yes from PID 1 might be *very* slow if the private directory contains many many files on slow disks thus blocking PID1 from continuing

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=68232

Lennart Poettering <lennart at poettering.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|big private temporary       |Cleaning up of /tmp
                   |directories stall systemd   |directories PrivateTmp=yes
                   |for a long time (many       |from PID 1 might be *very*
                   |hours)                      |slow if the private
                   |                            |directory contains many
                   |                            |many files on slow disks
                   |                            |thus blocking PID1 from
                   |                            |continuing

--- Comment #6 from Lennart Poettering <lennart at poettering.net> ---
Ah, hmm, I think I get it now.

If PrivateTmp is used and the private tmp dir is really really full of little
files, then we will try to delete them all synchronously stopping everything
else in PID 1 for that time and that might take ages. And that sucks hard.

Not sure what we can do about this... We could fork off the clean-up routine so
that PID 1 is unaffected by slow disk. But, brrr.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130912/c2aa75db/attachment.html>