All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Dave Jones <davej@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: futex hang with rpm in 2.6.17.1-2174_FC5
Date: Sat, 21 Oct 2006 10:45:02 -0700	[thread overview]
Message-ID: <453A5C9E.1070303@candelatech.com> (raw)
In-Reply-To: <20061021052423.GF21948@redhat.com>

Dave Jones wrote:
> On Fri, Oct 20, 2006 at 11:38:58AM -0700, Ben Greear wrote:
>  > I had a dead nfs server that was causing some programs to pause,
>  > in particular 'yum install foo' was paused.  I kill -9'd the
>  > yum related processes.
>  > 
>  > I fixed up the nfs server and was able to un-mount the file system.
>  > I subsequently killed many backed up updatedb and similar processes.
>  > 
>  > Now, there are no rpm processes, but if I try 'rpm [anything]' it
>  > hangs trying to open a futex:
>  > 
>  > open("/var/lib/rpm/Packages", O_RDONLY|O_LARGEFILE) = 4
>  > fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
>  > fstat64(4, {st_mode=S_IFREG|0644, st_size=41390080, ...}) = 0
>  > futex(0xb7ba178c, FUTEX_WAIT, 1, NULL <unfinished ...>
>  > 
>  > Is there any way to figure out what is causing this futex-wait?
>
> The dead rpm you killed left behind locks in its databases.
> rm -f /var/lib/rpm/__db* and it should work again.
>   
I'll give that a try, but shouldn't these locks clean themselves up when the
process is killed or shouldn't rpm notice the previous process is dead and
clean it up itself?

Thanks,
Ben

> 	Dave
>
>   


-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



  reply	other threads:[~2006-10-21 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:38 futex hang with rpm in 2.6.17.1-2174_FC5 Ben Greear
2006-10-21  5:24 ` Dave Jones
2006-10-21 17:45   ` Ben Greear [this message]
2006-10-21 18:00     ` Dave Jones
2006-10-21 18:08       ` Ben Greear
2006-10-21 21:55         ` Ulrich Drepper
2006-11-27  0:02         ` Denis Vlasenko

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=453A5C9E.1070303@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.