From owner-freebsd-current@FreeBSD.ORG Wed Mar 11 07:13:54 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 642111065678 for ; Wed, 11 Mar 2009 07:13:54 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 29BE78FC1C for ; Wed, 11 Mar 2009 07:13:54 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id n2A2Txs3003998; Mon, 9 Mar 2009 19:29:59 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (fw2.kientzle.com [10.123.1.2]) by monday.kientzle.com with SMTP id gj3fr8767jrukr872yt5ht73bn; Mon, 09 Mar 2009 19:29:59 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49B5D0A7.4070006@freebsd.org> Date: Mon, 09 Mar 2009 19:29:59 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pegasus Mc Cleaft References: <200903100104.53847.ken@mthelicon.com> In-Reply-To: <200903100104.53847.ken@mthelicon.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: bsdtar lockup on Current-03/10/2009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2009 07:13:56 -0000 Pegasus Mc Cleaft wrote: > > 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 just merged a lot of changes into FreeBSD-CURRENT. Any of the following would help me diagnose this: * libarchive and bsdtar have test suites: $ cd /usr/src/lib/libarchive && make check $ cd /usr/src/usr.bin/tar && make check Any errors are suspect. * A stack trace from gdb is most useful if both libarchive and bsdtar are built with debugging symbols: $ cd /usr/src/lib/libarchive $ make DEBUG_FLAGS=-g clean all install $ cd /usr/src/usr.bin/tar $ make DEBUG_FLAGS=-g clean all install $ gdb tar > run -cvf /dev/null / Control-C > bt * A system call trace is also very helpful: $ ktrace tar -cvf /dev/null * Email me the ktrace.out file. Any of the above would help me to narrow the problem down quite a bit. I'll also try to reproduce it here. Cheers, Tim