From owner-freebsd-current@FreeBSD.ORG  Fri Jan 28 14:47:35 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9009A16A4CE; Fri, 28 Jan 2005 14:47:35 +0000 (GMT)
Received: from green.homeunix.org (green@localhost [127.0.0.1])
	by green.homeunix.org (8.13.1/8.13.1) with ESMTP id j0SElYJJ097970;
	Fri, 28 Jan 2005 09:47:35 -0500 (EST)
	(envelope-from green@green.homeunix.org)
Received: (from green@localhost)
	by green.homeunix.org (8.13.1/8.13.1/Submit) id j0SElYhh097969;
	Fri, 28 Jan 2005 09:47:34 -0500 (EST)
	(envelope-from green)
Date: Fri, 28 Jan 2005 09:47:33 -0500
From: Brian Fundakowski Feldman <green@freebsd.org>
To: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <20050128144733.GA91982@green.homeunix.org>
References: <E1CuQFS-0003HK-MR@cs1.cs.huji.ac.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1CuQFS-0003HK-MR@cs1.cs.huji.ac.il>
User-Agent: Mutt/1.5.6i
cc: freebsd-current@freebsd.org
Subject: Re: dump is stuck
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2005 14:47:36 -0000

On Fri, Jan 28, 2005 at 09:08:54AM +0200, Danny Braniss wrote:
> hi,
> 	while running 'dump 0f - /dist | restore rf -'
> the dump proc. got stuck, it seems it's waiting on some lock:
> 
> UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
> 
>  0 30924 30922   0   4  0  3396 2852 sbwait T     p1    1:00.88 dump: 
> /dev/amrd0s3h: ...
>  0 30925 30924   1  -8  0  3268 2784 physrd TL    p1    0:53.84 dump 0f - 
> /dist (dump)
>  0 30926 30924   1  20  0  3268 2784 pause  T     p1    0:53.69 dump 0f - 
> /dist (dump)
>  0 30927 30924   1  20  0  3268 2784 pause  T     p1    0:54.12 dump 0f - 
> /dist (dump)
> 
> (this is  5.3-STABLE, cvs'ed about a week ago, and it's a SMP system).
> how can i find which lock? or who is holding it?

Is the one in physrd not actually reading anything from the disk right
now?  I would suspect that should be how you really determine if it's
hung or not.  You should be able to see how long it's been waiting
and how long it's due to wait still, using kgdb.

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\