From owner-freebsd-current@FreeBSD.ORG  Fri Jan 28 14:51:28 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 42DEF16A4CE; Fri, 28 Jan 2005 14:51:28 +0000 (GMT)
Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7F8B243D3F; Fri, 28 Jan 2005 14:51:27 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0SEp64R040315;
	Fri, 28 Jan 2005 15:51:06 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Brian Fundakowski Feldman <green@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 28 Jan 2005 09:47:33 EST."
             <20050128144733.GA91982@green.homeunix.org> 
Date: Fri, 28 Jan 2005 15:51:06 +0100
Message-ID: <40314.1106923866@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
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:51:28 -0000

In message <20050128144733.GA91982@green.homeunix.org>, Brian Fundakowski Feldman writes:
>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.

Check also with gstat(8) if there is I/O activity going on and/or if any
I/O requests are stuck.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.