From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Sixt Subject: Re: [PATCH v2] compat: Fix read() of 2GB and more on Mac OS X Date: Mon, 19 Aug 2013 10:40:52 +0200 Message-ID: <5211DA14.3020501@kdbg.org> References: <1376743205-12618-1-git-send-email-prohaska@zib.de> <1376894300-28929-1-git-send-email-prohaska@zib.de> <5211D544.8080706@kdbg.org> <5211D697.7020107@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Steffen Prohaska , Junio C Hamano , git@vger.kernel.org, John Keeping , Jonathan Nieder , "Kyle J. McKay" , =?UTF-8?B?VG9yc3RlbiBCw7ZnZXJzaGF1cw==?= =?UTF-8?B?ZW4=?= To: Stefan Beller X-From: git-owner@vger.kernel.org Mon Aug 19 10:41:11 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VBL1T-0001fO-6b for gcvg-git-2@plane.gmane.org; Mon, 19 Aug 2013 10:41:11 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750988Ab3HSIlG (ORCPT ); Mon, 19 Aug 2013 04:41:06 -0400 Received: from bsmtp1.bon.at ([213.33.87.15]:3373 "EHLO bsmtp.bon.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750904Ab3HSIlF (ORCPT ); Mon, 19 Aug 2013 04:41:05 -0400 Received: from [10.67.83.65] (178.115.251.65.wireless.dyn.drei.com [178.115.251.65]) by bsmtp.bon.at (Postfix) with ESMTP id 2AB3010029; Mon, 19 Aug 2013 10:40:58 +0200 (CEST) User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 In-Reply-To: <5211D697.7020107@googlemail.com> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Am 19.08.2013 10:25, schrieb Stefan Beller: > On 08/19/2013 10:20 AM, Johannes Sixt wrote: >> Am 19.08.2013 08:38, schrieb Steffen Prohaska: >>> +test_expect_success EXPENSIVE 'filter large file' ' >>> + git config filter.largefile.smudge cat && >>> + git config filter.largefile.clean cat && >>> + for i in $(test_seq 1 2048); do printf "%1048576d" 1; done >2GB && >> >> Shouldn't you count to 2049 to get a file that is over 2GB? > > Would it be possible to offload the looping from shell to a real > program? So for example > truncate -s 2049M > should do the job. That would create a file reading all bytes as zeros > being larger as 2G. If truncate is not available, what about dd? The point is exactly to avoid external dependencies. Our dd on Windows doesn't do the right thing with seek=2GB (it makes the file twice as large as expected). -- Hannes