Thanks,

Jason

I've only ever seen that in two situations.

1) The file is still open by a process.  You say you've checked that
   with lsof.  I sometimes use 'find /proc -type f -links 0'.  

2) You're using vxfs.  Sometimes VxFS filesystems will not show the
   available space for a short period of time.  It appears that some of
   the work continues in the background.  After a short period of time,
   the 'df' reappears.

--
Darren Dunham                                           ddun...@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Another way, if you really need to know, is to run "fsck -n"
on the device for the filesystem.  Note the "-n" -- it's
very important, because without it, the filesystem might be
opened for writing.

If you have a file that's open but "deleted" (from the directory),
it will show up as an unreferenced file.

   - Logan

The only explanation I can think of is that running processes *are*
holding open the deleted files.  How did you use lsof to check?  
Remember that you can't check by filename any more, because the
deleted files no longer have one...
--
             Christopher Mattern

"Which one you figure tracked us?"
"The ugly one, sir."
"...Could you be more specific?"

There is also the possibility that the file is linked into more
than one directory.  For example:

        dd if=/dev/zero of=foo bs=1024k count=100
        ln foo bar
        df -k .
        rm foo
        df -k .

If you do this, the "rm foo" won't cause the "df" to show any
more free space.  But if you then do "rm bar", it will free
up the space.

   - Logan