fuser only sees what files are held open by processes. If there's anything
else keeping the file open, it won't know. So all no fuser output tells
you is "it's no process - at least not directly".
> [ File was held open by a loop device ]
>
> Maybe fuser needs updating to take account of this. It's very misleading
> when it tells you nothing's using a filesystem, and yet the kernel still
> tells you the filesystem's busy when you try to umount it.
Hmm, there doesn't seem to be any related information in /proc, so fuser
has no way of figuring that out. Swap files and such should cause similar
problems. If somebody adds that information to /proc, I'll be glad to
teach fuser about it.
- Werner
-- _________________________________________________________________________ / Werner Almesberger, DI-LRC,EPFL,CH werner.almesberger@lrc.di.epfl.ch / /_IN_R_133__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/