Why is /tmp/jack busy?
On Sat, Jun 28, 2008 at 12:08 PM, PaulNM <email@example.com> wrote:
> Mark Knecht wrote:
>> and what's with this time stamp value?
>> When I boot this machine it gets to a point where it says something
>> like 'Wiping /tmp...' and then I see a message 'Unable to remove
>> ./jack' and then something about the device or directory being busy.
>> When I log in as root and try to remove it by hand this is the
>> lightning tmp # ls -la
>> total 24
>> drwxrwxrwt 5 root root 8192 2008-06-28 07:12 .
>> drwxr-xr-x 25 root root 4096 2008-05-04 18:23 ..
>> drwxrwxrwt 2 root root 4096 2008-06-28 07:10 .ICE-unix
>> drwxrwxrwt 2 root root 40 2008-06-28 00:10 jack
>> -r--r--r-- 1 root root 11 2008-06-28 07:10 .X0-lock
>> drwxrwxrwt 2 root root 4096 2008-06-28 07:10 .X11-unix
>> lightning tmp # rm -rf jack/
>> rm: cannot remove directory `jack': Device or resource busy
>> lightning tmp #
>> Two questions to start:
>> 1) If /tmp/jack is really busy then who is using it? This machine was
>> cold booted 9 minutes ago and Jack (the sound connection machine)
>> isn't running:
>> lightning tmp # ps aux | grep jack
>> root 5635 0.0 0.0 4096 696 pts/0 R+ 07:20 0:00 grep
>> --colour=auto jack
>> lightning tmp #
> Try lsof: "lsof /tmp/jack" or "lsof | grep jack" since I'm not sure if lsof
> works on directories alone.
> Also, are you sure /tmp/jack is empty? Did you "ls -a" ?
>> Thanks in advance,
Yes, ls -al shown nothing is there.
Actually, I think the root cause of this is a little different than
I expected. /tmp/jack is actually something that's mounted:
lightning ~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
none 508016 0 508016 0% /tmp/jack
and the root cause of that is that it's in my fstab file:
lightning ~ # cat /etc/fstab | grep jack
none /tmp/jack tmpfs defaults 0 0
lightning ~ #
So, there are three directions to go:
1) Remove it from fstab and figure out what the repercussions of that
action might be.
2) Understand why the Gentoo boot process want to wipe mounted
directories in /tmp since it won't work.
3) Go back to ignoring it.
I'm going to investigate #1 first as this is something that I think
is left over from years ago, but maybe you or someone else has another
firstname.lastname@example.org mailing list