X-Spam-Checker-Version: SpamAssassin 3.4.0-r929098 (2010-03-30) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.4.0-r929098 Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p1JKVHOi038478 for ; Sat, 19 Feb 2011 14:31:17 -0600 X-ASG-Debug-ID: 1298147638-2ee2013a0000-NocioJ X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from greer.hardwarefreak.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id C770A1DD57C2 for ; Sat, 19 Feb 2011 12:33:58 -0800 (PST) Received: from greer.hardwarefreak.com (mo-65-41-216-221.sta.embarqhsd.net [65.41.216.221]) by cuda.sgi.com with ESMTP id lwyuuEiU1bWKCbNb for ; Sat, 19 Feb 2011 12:33:58 -0800 (PST) Received: from [192.168.100.53] (gffx.hardwarefreak.com [192.168.100.53]) by greer.hardwarefreak.com (Postfix) with ESMTP id 1F7916C130 for ; Sat, 19 Feb 2011 14:33:58 -0600 (CST) Message-ID: <4D602936.10400@hardwarefreak.com> Date: Sat, 19 Feb 2011 14:33:58 -0600 From: Stan Hoeppner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: xfs@oss.sgi.com X-ASG-Orig-Subj: Re: External log size limitations Subject: Re: External log size limitations References: <4D5C1D77.1060000@spinpro.com> <20110217003233.GH13052@dastard> <4D5E8FAD.9080802@spinpro.com> <4D5ECEC5.2020701@hardwarefreak.com> <4D5ED70B.7030504@spinpro.com> <4D5F3EBF.3030309@hardwarefreak.com> <20110219100207.GA24537@citd.de> In-Reply-To: <20110219100207.GA24537@citd.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Barracuda-Connect: mo-65-41-216-221.sta.embarqhsd.net[65.41.216.221] X-Barracuda-Start-Time: 1298147638 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -1.42 X-Barracuda-Spam-Status: No, SCORE=-1.42 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests=BSF_SC5_MJ1963, RDNS_DYNAMIC X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.55815 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.10 RDNS_DYNAMIC Delivered to trusted network by host with dynamic-looking rDNS 0.50 BSF_SC5_MJ1963 Custom Rule MJ1963 X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on oss.sgi.com X-Virus-Status: Clean Matthias Schniedermeyer put forth on 2/19/2011 4:02 AM: > On 18.02.2011 21:53, Stan Hoeppner wrote: >> Fist, sorry for the length. I can tend to get windy talking shop. :) >> >> Andrew Klaassen put forth on 2/18/2011 2:31 PM: >> >>> It's IBM and LSI gear, so I'm crossing my fingers that a Linux install >>> will be relatively painless. >> >> Ahh, good. At least, so far it seems so. ;) >> >>> I thought that the filesystem block size was still limited to the kernel >>> page size, which is 4K on x86 systems. >>> >>> http://oss.sgi.com/projects/xfs/ >>> >>> "The maximum filesystem block size is the page size of the kernel, which >>> is 4K on x86 architecture." >>> >>> Is this no longer true? It would be awesome news if it wasn't. >> >> My mistake. It would appear you are limited to the page size, which, as >> I mentioned, is still 8 KiB for most distros. > > You confuse that with STACK-size. Yes, I did. However... > The page-size is, and has always been, 4 KiB (on X86). To bring this back around to the OP's original question, do you agree or disagree with my assertion that a 64 KiB XFS block size will yield little if any advantage over a 4 KiB block size, and may in fact have some disadvantages, specifically with small file random IO? -- Stan