All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Joe Pruett <joey@clean.q7.com>
Cc: autofs@linux.kernel.org
Subject: Re: something changed from 4 to 5
Date: Sun, 24 Aug 2008 13:11:55 +0800	[thread overview]
Message-ID: <48B0ED9B.5080103@themaw.net> (raw)
In-Reply-To: <alpine.LRH.1.10.0808232150000.7557@q7.q7.com>

Joe Pruett wrote:
>> Took me a while to work out what you had done here.
>> To get the backtrace you need only connect to the main thread (in 
>> this case 1741) and do the "thr a a bt".
>> That gives backtrace info for all the sub-threads at once, which is 
>> what we need.
>
> this is a centos 5 box so the other pids from ps are standalone 
> processes (look at the lwp list from the first gdb to see that they 
> aren't the same).
>
> the first gdb should have been the data you want. by connecting to the 
> other pids, it eventually unblocks whatever is stuck and then the 
> world starts working again. oddly, it seems to be a call to access 
> that is hung. in the past i've just used strace and could never tell 
> what was stuck.

And the call to access(2) is seen in the first backtrace as waiting on 
an nfs mount and any other processes calling to access(2) should wait on 
the first in this case, since the path includes the same mount.

When this happens you could also try looking for mount processes to 
match them to those in the backtraces but if any have died that should 
result in the daemon continuing. So it's a bit puzzling.

Ian

  reply	other threads:[~2008-08-24  5:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 16:53 something changed from 4 to 5 Joe Pruett
2008-08-13  2:58 ` Ian Kent
2008-08-13  4:11   ` Joe Pruett
2008-08-23 14:45   ` Joe Pruett
2008-08-24  4:32     ` Ian Kent
2008-08-24  4:58       ` Joe Pruett
2008-08-24  5:11         ` Ian Kent [this message]
2008-08-24 14:48           ` Joe Pruett
2008-08-25  2:14             ` Ian Kent
2008-08-25  2:42               ` Joe Pruett
2008-08-24  4:54     ` Ian Kent
2008-08-24  5:27       ` Ian Kent
2008-09-02 22:07   ` Joe Pruett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48B0ED9B.5080103@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=joey@clean.q7.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.