From owner-freebsd-current@FreeBSD.ORG  Mon Sep 10 11:28:29 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2BBF416A419
	for <freebsd-current@freebsd.org>; Mon, 10 Sep 2007 11:28:29 +0000 (UTC)
	(envelope-from Thomas.Sparrevohn@btinternet.com)
Received: from smtp802.mail.ird.yahoo.com (smtp802.mail.ird.yahoo.com
	[217.146.188.62])
	by mx1.freebsd.org (Postfix) with SMTP id 6018413C45D
	for <freebsd-current@freebsd.org>; Mon, 10 Sep 2007 11:28:28 +0000 (UTC)
	(envelope-from Thomas.Sparrevohn@btinternet.com)
Received: (qmail 66507 invoked from network); 10 Sep 2007 11:28:27 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com;
	h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
	b=GA7rckr1rktmM7BXEIjEr6oLax1VVB8SvOsXOksO91aDmmz+jcQ44mBzvkoLzrtncJURVxCc3ByeX38A+Fp2VQ4gZqPmoewKPg4meIEoD2z7EzrbhKRa/EZci7fll/G114JylbsZJkXqJ21xrS1POtXMsEit0uMYE1x0es/UE6E=
	; 
Received: from unknown (HELO w2fzz0vc03.aah-go-on.com)
	(thomas.sparrevohn@btinternet.com@86.133.55.166 with login)
	by smtp802.mail.ird.yahoo.com with SMTP; 10 Sep 2007 11:28:26 -0000
X-YMail-OSG: ZKXx4hcVM1lecdiFeAmvtkGDDeXNCBYz1j0.nsHnQK0I6Fy9qmfv0u5nTSTugNZyeJHc3R5fgQ--
From: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com>
To: freebsd-current@freebsd.org
Date: Mon, 10 Sep 2007 12:28:25 +0100
User-Agent: KMail/1.9.7
References: <E1ISdQi-000GkC-4v@cs1.cs.huji.ac.il>
	<046801c7f229$a4534510$ecf9cf30$@co.uk>
	<E1IUcXc-000NdZ-LH@cs1.cs.huji.ac.il>
In-Reply-To: <E1IUcXc-000NdZ-LH@cs1.cs.huji.ac.il>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200709101228.25867.Thomas.Sparrevohn@btinternet.com>
Subject: Re: dump problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Mon, 10 Sep 2007 11:28:29 -0000

On Monday 10 September 2007 07:14:36 Danny Braniss wrote:
> > > 
> > > the only indication I can see, is that one of the dump procs. is
> > > waiting on
> > > sbwait, and probably it's some deadlock, which is similar to what I
> > > keep
> > > seeing here, i'll try now with SCHED_ULE to see if it make a
> > > difference.
> > 
> > 
> > I'm running SCHED_ULE on these already, if your not I guess it's not the
> > scheduler?
> > 
> I can get it to 'work' by fiddling with the b flag (blocksize), which still
> points to some timming/deadlock problem.
> ie:
> 	dump 0abf 64 /some/backup/file  /file/to/backup
> now works, but
> 	dump 0abf 64 - | restore rbf 64 - 
> hangs as before. (i don't think the b 64 in restore is needed).

I have been able to reproduce the deadlock with any configuration - just using the dump
part - never found out what caused it.