Christophe TROESTLER <[EMAIL PROTECTED]> writes: > On Mon, 29 May 2000, Dan Christensen <[EMAIL PROTECTED]> wrote: > > > > Is there an easy way to determine what makes a filesystem busy, e.g. > > what prevents me from remounting /usr readonly after an upgrade? > > Usually some file that was erased is being held open by a process, > > but I don't know an easy way to determine which file or process. > > "lsof | grep usr" is a start, but provides too long a list. Is > > there an easier way? > > man fuser
Does that really do what I want? It seems like that would tell me what I can't *unmount* a filesystem, but I want to find out why I can't remount a filesystem readonly. "fuser -m /usr" produces about 70 pids... Dan
