[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

determining what makes a filesystem busy



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?

Dan



Reply to: