From owner-freebsd-current@FreeBSD.ORG Tue Mar 10 05:15:04 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 F02B6106566C for ; Tue, 10 Mar 2009 05:15:04 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: from mail-fx0-f158.google.com (mail-fx0-f158.google.com [209.85.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 804288FC14 for ; Tue, 10 Mar 2009 05:15:04 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: by fxm2 with SMTP id 2so1382481fxm.43 for ; Mon, 09 Mar 2009 22:15:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:message-id:user-agent:mime-version:content-type; bh=fEs/4+kHplsxE55UkLh4yqiHfgYo5tPzi9o4ZcwLeoo=; b=JCZc13MKLP9CuSth3jY92zKvuoTe5rpKBGIow2mt2Pg7y170dvtj9aTq2hH28nNBNL mkt89A5f8ZSkcxrbL0D70OTs5RNtbtEcZcr2/hXeP2sr5kToleOki/bn5BD/hgXtw9mK Zw0SlblY8ZojLR4jcSNowRaQ+V0hCuvWJI/KM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:message-id:user-agent :mime-version:content-type; b=FzscraheNerZNhMVawMo11W8v6HsEEl/8OFTtfq8iffVGnSj8+oEamvyWfv3VIB31J ltxzZiiFpwcP3nCBiZrxbiHnEyM2Eie1EF3sTA0tEn184F1AsJtziXH5c7JuCWCxahKr fxrdXFv83maSH+ylIhI+eTcQoNuPrH30m0sLw= Received: by 10.86.89.20 with SMTP id m20mr1628588fgb.14.1236660433029; Mon, 09 Mar 2009 21:47:13 -0700 (PDT) Received: from localhost (93-80-44-184.broadband.corbina.ru [93.80.44.184]) by mx.google.com with ESMTPS id 4sm4547633fge.34.2009.03.09.21.47.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Mar 2009 21:47:12 -0700 (PDT) From: Anonymous To: Pegasus Mc Cleaft References: <200903100104.53847.ken__6247.10998167775$1236647281$gmane$org@mthelicon.com> Date: Tue, 10 Mar 2009 07:46:43 +0300 Message-ID: <86mybuasss.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Tue, 10 Mar 2009 05:15:05 -0000 Pegasus Mc Cleaft writes: > 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 This was already reported in bin/132452. Can you go to src/usr.bin/tar and update it up before r189514 such as r189513? BTW, do you have same problem with `rsync -X' on ZFS partition?