From owner-freebsd-hackers@FreeBSD.ORG  Tue Mar 10 01:04:56 2009
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BE98C106566C;
	Tue, 10 Mar 2009 01:04:56 +0000 (UTC)
	(envelope-from ken@mthelicon.com)
Received: from hercules.mthelicon.com (hercules.mthelicon.com
	[IPv6:2001:49f0:2023::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 8AEB98FC20;
	Tue, 10 Mar 2009 01:04:56 +0000 (UTC)
	(envelope-from ken@mthelicon.com)
Received: from feathers.peganest.com (78-33-110-3.static-adsl.entanet.co.uk
	[78.33.110.3] (may be forged)) (authenticated bits=0)
	by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n2A14sdA099826
	(version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO);
	Tue, 10 Mar 2009 01:04:55 GMT (envelope-from ken@mthelicon.com)
From: Pegasus Mc Cleaft <ken@mthelicon.com>
Organization: Feathers
To: current@freebsd.org, hackers@freebsd.org
Date: Tue, 10 Mar 2009 01:04:53 +0000
User-Agent: KMail/1.11.0 (FreeBSD/8.0-CURRENT; KDE/4.2.0; amd64; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200903100104.53847.ken@mthelicon.com>
Cc: 
Subject: bsdtar lockup on Current-03/10/2009
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2009 01:04:57 -0000

Hi Current & Hackers, 

	I was wondering if anyone else is seeing this problem: Any use of bsdtar to 
create a new archive causes the process to be unresponsive to all signals and 
consumes 100% cpu time. The machine I am testing on is a Core 2 quad running 
in AMD64 (8 gigs ram, zfs boot, root, et al.)

	I have tried disabling the zil and prefetch as a precaution but can still 
cause the failure by doing the command below(trying to eliminate zfs writes as 
being the problem):
#tar -cvf /dev/null *

	Unarchiving from tar seems to work OK. The bug may have been introduced a few 
days ago. I just noticed my machine doing this tonight when I tried to do a 
portupgrade and the creation of the backups locked up. 

Thanks, 
Peg