From owner-freebsd-hackers@FreeBSD.ORG  Thu Oct 30 12:32:34 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 93CEBFF4;
 Thu, 30 Oct 2014 12:32:34 +0000 (UTC)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com
 [IPv6:2a00:1450:400c:c05::22f])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0A8B83F9;
 Thu, 30 Oct 2014 12:32:33 +0000 (UTC)
Received: by mail-wi0-f175.google.com with SMTP id ex7so4379393wid.2
 for <multiple recipients>; Thu, 30 Oct 2014 05:32:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=date:from:to:subject:message-id:in-reply-to:references:mime-version
 :content-type:content-transfer-encoding;
 bh=4gpFkc9aIVg9uza1gVEI8MMLj+IRQaa6kKxP64rST4E=;
 b=qS61e8dJISxCnfgwV1STRtesKXj8iKGj/8ko7ACu8SbJm8RWY5NxFmpusjAFOTu8uY
 eVR873q/KMrcHWMQ4SEXFN2mAIEcy2+17g8qxvUjd4MhpdmH7Yz6By3o8PWUThjCQb0G
 vVGLPjd3F0YaUoW79x+UhRbFFxHzpYF1dl+qZs5METgNh2VM1peQVKufm9ZWZVR8TBM4
 Ey1LdjhCtKRm2TuZaGCRY1WO+DtWda5oN4omDqf1+1wSdEzZLicgq0XOosngjiU/kwtW
 jnx4iAwDcvm3cfqcAvAN2y1IQWhOHbPj2ApT3Dj5ksWixm7YfMMnu3iwLgXt8A3d+JVw
 PEbQ==
X-Received: by 10.194.61.99 with SMTP id o3mr19787083wjr.54.1414672352373;
 Thu, 30 Oct 2014 05:32:32 -0700 (PDT)
Received: from localhost ([82.193.208.225])
 by mx.google.com with ESMTPSA id n4sm8191720wjb.40.2014.10.30.05.32.31
 for <multiple recipients>
 (version=SSLv3 cipher=RC4-SHA bits=128/128);
 Thu, 30 Oct 2014 05:32:31 -0700 (PDT)
Date: Thu, 30 Oct 2014 13:32:30 +0100
From: <rank1seeker@gmail.com>
To: Allan Jude <allanjude@freebsd.org>, freebsd-hackers@freebsd.org
Subject: Re: tar behavior 9.* -> 10.*
Message-ID: <20141030133230.00004204@gmail.com>
In-Reply-To: <544A6595.2070204@freebsd.org>
References: <20141024141552.000048ac@gmail.com> <544A6595.2070204@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Thu, 30 Oct 2014 12:32:34 -0000

On Fri, 24 Oct 2014 10:43:33 -0400
Allan Jude <allanjude@freebsd.org> wrote:

> On 2014-10-24 08:15, rank1seeker@gmail.com wrote:
> > https://forums.freebsd.org/threads/tar-errors-when-file-content-extracted-to-stdout-is-piped.48626/
> > 
> > Bug?
> > _______________________________________________

> What happens if you pipe it to something that doesn't close the pipe
> prematurely
> 
> try:
> 
> tar ... | cat -
> 
> It makes sense that it throws an error when you pipe to head, which
> then closes the pipe before the file has finished being written.
> 

Even in it's "cleanest form" it hangs:
# tar -xOf src.txz usr/src/UPDATING
Outputed complete content immidieatly to STDOUT and then hanged for 56
seconds!

With your code situation is same.

To cut it short, this is a non critical bug fixed in 9.*, aka tar
regression.