Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2.fluke 9/24/84; site fluke.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!vax135!cornell!uw-beaver!fluke!joe From: joe@fluke.UUCP (Joe Kelsey) Newsgroups: net.bugs.4bsd Subject: 4.2 hangs with locked root inode Message-ID: <2147@vax4.fluke.UUCP> Date: Tue, 12-Feb-85 18:25:18 EST Article-I.D.: vax4.2147 Posted: Tue Feb 12 18:25:18 1985 Date-Received: Thu, 14-Feb-85 00:44:43 EST Organization: John Fluke Mfg. Co., Inc., Everett, WA Lines: 17 Index: Probably sys/{ufs,sys}_inode.c Description: We occaisionally have systems hang in such a state that no useful work seems to be getting done. When we force a crash, the dump reveals several interesting facts: 1) Almost no runnable processes. If there are any runnable processes, it's usually something inoccuous like rwhod. 2) LOTS of processes stuck in disk wait, with WCHAN pointing to the ROOT INODE! Also, the root inode has ILOCK|IWANT set, indicating someone locked it and lots of people want it (count is large). Repeat-By: I really don't know how to repeat this. It seems to occur randomly enough that I can't seem to pin down the cause. How do you tell which process has set a lock on an inode that others want to access? /Joe Kelsey