On Tue, Jan 07, 2020 at 10:16:22AM -0700, Raymond, David wrote: > On an AMD-64 workstation /tmp fills up to 105% according to df, > apparently as a result of UNIX pipes in a shell script passing a whole > lot of moderately big files. Examination of /tmp with du and ls -gal > on /tmp shows no big files and trying to delete everything that is > there has no effect. Rebooting cleans out /tmp. > > I had /tmp mounted with the standard options + softdep. I eliminated > softdep and the problem appears to have gone away. > > Any ideas on what is going on with softdep here? Dmesg shows a long > series of "/tmp file system full" messages.
If you're using current and that started to happens in the last week or so, then maybe there is some bug somewhere in the softdep code. Some devs are reworking some parts of softdep. If the problem is not new or you're using -stable, then maybe the problem is that you're using a too small /tmp partition. Softdep delays the writing of metadata. Maybe you're writing and deleting too much data without giving softdep a chance to update the metadata on the disk. Giving more space to /tmp should fix the problem. Even if you're not going to use so much space, softdep will need the extra space between the metadata updates. BTW, I prefer to use "async" for /tmp. -- Juan Francisco Cantero Hurtado http://juanfra.info
