sub-directory 'hung' ...

[David Schultz]

On Sun, Jun 08, 2003, Marc G. Fournier wrote:
> 
> 'K, not sure how/what to debug here ...
> 
> doing a grep of svr1.postgresql.org in /proc/*/status shows all the
> processes 'stuck' in inode ...
> 
> /proc/38750/status:inetd 38750 2072 2072 2072 -1,-1 noflags 1055120147,191009 0,0 0,592 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org
> /proc/38752/status:inetd 38752 2072 2072 2072 -1,-1 noflags 1055120154,886433 0,0 0,637 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org
> /proc/38753/status:inetd 38753 2072 2072 2072 -1,-1 noflags 1055120155,641964 0,0 0,610 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org
> /proc/38806/status:inetd 38806 2072 2072 2072 -1,-1 noflags 1055120188,905284 0,0 0,789 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org
> /proc/38863/status:inetd 38863 2072 2072 2072 -1,-1 noflags 1055120257,763084 0,0 0,656 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org
[...]
> I'm going to get the server rebooted, don't know if a ctl-alt-esc will get
> us a core though, but will try ... assuming that it doesn't, is there
> anything that I should run to get more information when something like
> this happens?

A backtrace on the processes stuck in kernel mode might shed some
light on the deadlock.  (To get a backtrace of the process with
pid N from DDB, just say 'trace N'.)