From owner-freebsd-current@FreeBSD.ORG Wed Mar 11 06:41:58 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 DA83F1065673 for ; Wed, 11 Mar 2009 06:41:58 +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 23A5B8FC2D for ; Wed, 11 Mar 2009 06:41:58 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id n2B4ZcpY019176; Tue, 10 Mar 2009 21:35:38 -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 f5we35vi5wu22thzanj5dg7b5w; Tue, 10 Mar 2009 21:35:38 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49B73F99.9010200@freebsd.org> Date: Tue, 10 Mar 2009 21:35:37 -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: John Nielsen References: <200903100104.53847.ken__6247.10998167775$1236647281$gmane$org@mthelicon.com> <200903101238.20974.paul@fletchermoorland.co.uk> <86sklldth2.fsf@gmail.com> <200903102310.32735.lists@jnielsen.net> In-Reply-To: <200903102310.32735.lists@jnielsen.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: ZFS/extattr lockup (was 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:41:59 -0000 John Nielsen wrote: > > I today noticed the same problem on -CURRENT i386 built March 9. > ... using ZFS and initially > thought that was the source of the regression but I haven't produced the > lockup with anything but tar and the extattr removal hack seems to have > fixed it for now ... The common element so far seems to be ZFS. Can you verify that $ lsextattr -h user hangs on your system as well? That invokes the same extattr_list_link system call used by tar to enumerate the extended attributes on a file. The recent updates to tar made it one of the first really common utilities to support extended attributes so I wouldn't be at all surprised if this had been broken for some time. Tim