Re: determining what makes a filesystem busy
Dan Christensen wrote:
>
> Christophe TROESTLER <ev_galois@freegates.be> writes:
> > On Mon, 29 May 2000, Dan Christensen <jdc@jhu.edu> 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...
I don't know if it would work or even be recommended but have you tried
the -k option to kill all processes to that file system? The other
thought I had is boot into your system as a single user but I'm sure
that is what your trying to avoid, is a boot.
hth,
kent
Reply to: