On Tue, 14 Sep 2004 23:30:39 +0700, Maxim Shilov <mshilov@xxxxxxxxxxx> wrote: > Lukas Ruf wrote: > >> The process is the usual "df" command , which is hanging on > >> invocation . The system responds to other commands and is not > >> hung up. This is typical of an nfs mount somewhere not responding because a server went walkies (in fact very likely given the trace in your original post). Probably worth mounting these shares with the soft mount option in any case Lukas. > >> Not sure if it is taking any uninterruptible kernel code path. Well the state given obviously suggests that it's blocking waiting for some IO that never comes in. > D-state means that process cannot acomplish input/output operation. You > can't kill it. No. It means that it is in UNINTERRUPTIBLE sleep but does not imply anything about the ability for the IO that it is likely waiting on to complete. You can't kill it because it won't receive any signals that you send to it - the difference between UNINTERRUPTIBLE and INTERRUPTIBLE sleep. > One of the possible reasons is hardware problems. Or the network cable got unplugged...or a server went awry...or the cleaner down the hall tried to find a spare mains plug outlet to use... Jon. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
