Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E09B72E2D97 for ; Fri, 14 Mar 2008 03:35:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 88772-04 for ; Fri, 14 Mar 2008 03:35:39 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from shrek.krogh.cc (2605ds1-ynoe.1.fullrate.dk [90.184.12.24]) by postgresql.org (Postfix) with ESMTP id 2F36F2E007F for ; Fri, 14 Mar 2008 03:35:39 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id 4743A3BF212; Fri, 14 Mar 2008 07:17:02 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id txm8fhDEvIhk; Fri, 14 Mar 2008 07:16:53 +0100 (CET) Received: from [192.168.1.5] (unknown [90.184.13.46]) by shrek.krogh.cc (Postfix) with ESMTP id 58B283BF179; Fri, 14 Mar 2008 07:16:53 +0100 (CET) Message-ID: <47DA1866.3050500@krogh.cc> Date: Fri, 14 Mar 2008 07:17:10 +0100 From: Jesper Krogh User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Scott Marlowe CC: justin , pgsql-performance@postgresql.org Subject: Re: Benchmark: Dell/Perc 6, 8 disk RAID 10 References: <3E9C3A51-C28E-4B75-9739-E344DAC72880@fastcrypt.com> <47D00DB2.7040007@emolecules.com> <18451.1204824562@sss.pgh.pa.us> <47D0AFC1.5070305@emolecules.com> <08115901408538@mail.emproshunts.com> <47D93A43.6020503@emolecules.com> <016301c8854e$851e06e0$3101a8c0@JDell> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/300 X-Sequence-Number: 29254 Scott Marlowe wrote: > On Thu, Mar 13, 2008 at 3:09 PM, justin wrote: > >> I chose to use ext3 on these partition > > You should really consider another file system. ext3 has two flaws > that mean I can't really use it properly. A 2TB file system size > limit (at least on the servers I've tested) and it locks the whole > file system while deleting large files, which can take several seconds > and stop ANYTHING from happening during that time. This means that > dropping or truncating large tables in the middle of the day could > halt your database for seconds at a time. This one misfeature means > that ext2/3 are unsuitable for running under a database. I cannot acknowledge or deny the last one, but the first one is not true. I have several volumes in the 4TB+ range on ext3 performing nicely. I can test the "large file stuff", but how large? .. several GB is not a problem here. Jesper -- Jesper