From owner-freebsd-current@FreeBSD.ORG Wed Mar 11 06:41:59 2009 Return-Path: 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 C9F9B1065676 for ; Wed, 11 Mar 2009 06:41:59 +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 5EBE48FC32 for ; Wed, 11 Mar 2009 06:41:59 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id n2B1a0ZC017502; Tue, 10 Mar 2009 18:36:00 -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 wf5fj8yu88hkje9k3n5xi64f4i; Tue, 10 Mar 2009 18:35:59 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49B7157F.7010101@freebsd.org> Date: Tue, 10 Mar 2009 18:35: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: Anonymous References: <200903100104.53847.ken__6247.10998167775$1236647281$gmane$org@mthelicon.com> <86mybuasss.fsf@gmail.com> <200903101238.20974.paul@fletchermoorland.co.uk> <86sklldth2.fsf@gmail.com> In-Reply-To: <86sklldth2.fsf@gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Pegasus Mc Cleaft , Paul Wootton 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 06:42:00 -0000 Anonymous wrote: > Paul Wootton writes: > >>Im also using ZFS and have the same problems as Peg when trying to create a >>tar file. >>This is using Current as of last yesterday (09-mar-09). > > I'm not sure but in my case ktrace shows extattr_list_link() before the lockup. > So, for a workaround I disabled extattr support in libarchive. Can you verify that > this helps you, too? Please try this, which will poke that same system call in a different way: rm -f foo foolink touch foo ln -s foo foolink lsextattr -h user foolink lsextattr -h user foo setextattr user test test foo lsextattr -h user foolink lsextattr -h user foo setextattr user test test foolink lsextattr -h user foolink I'm especially curious about the processor and filesystem you're using when you see these problems. Cheers, Tim