From owner-freebsd-stable@FreeBSD.ORG Sun Oct 5 09:34:37 2014 Return-Path: Delivered-To: freebsd-stable@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 71461F6D for ; Sun, 5 Oct 2014 09:34:37 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08CB8C75 for ; Sun, 5 Oct 2014 09:34:36 +0000 (UTC) Received: from walrus.pepperland ([81.217.76.60]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MOfQw-1XXx3b1FOI-0063Hn; Sun, 05 Oct 2014 11:34:29 +0200 Message-ID: <543110A4.7040505@gmx.net> Date: Sun, 05 Oct 2014 11:34:28 +0200 From: Stefan Ehmann User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Mark Felder , freebsd-stable@freebsd.org Subject: Re: xzgrep: incomplete results on larger files References: <541DE9FC.2090003@gmx.net> <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com> In-Reply-To: <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:T2g+e9HcGq0BrAyR/92/0c1ncli0d9jT1jVRsB8crLpq61FB7QP oQdeVUHPacJbWu0WXkF2Ozp0UllOdFDlP+dLYSnOQHoqjKo3ZtRe50aNGvETZgWX2XeXk0A OTO9Qwe7tBmmz6Hi3T+9h42zDhRDdCXwPim+C45MhBMpbuf2vcJx98w1BL3iH9BZwdumdzD AfbjJAKljhfWg5nrP58yw== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2014 09:34:37 -0000 On 29.09.2014 16:14, Mark Felder wrote: > > > On Sat, Sep 20, 2014, at 15:56, Stefan Ehmann wrote: >> I observed the following behavior on 10.1-BETA1 r271683M (amd64): >> >> xzgrep doesn't search the complete file: >> $ seq 10000 | xz > seq.xz >> $ xzgrep -c . seq.xz >> 6775 >> >> Using regular grep works as expected: >> $ xzcat seq.xz | grep -c . >> 10000 >> >> Processing seems to stop after 32KB (uncompressed). >> > > Wow, this is bizarre... Compression with xz is getting more and more > popular. This may have bit me a few times and I didn't even know it! > > I'll see what I can to do bring this to someone's attention. Any progress on this issue? Would have been nice if 10.1 included the patch and had a working xzgrep. But it's probably already a bit late for that.