Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 32E0F2E2F00 for ; Fri, 14 Mar 2008 03:19:45 -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 81582-01 for ; Fri, 14 Mar 2008 03:19:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by postgresql.org (Postfix) with ESMTP id 267E12E2F3A for ; Fri, 14 Mar 2008 03:19:42 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id m38so4404804waf.5 for ; Thu, 13 Mar 2008 23:19:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=iZ23DWU53+BGqwJgx3hfT+aFOpV4F+52qSMamPhT8Ws=; b=o/eBiRyyfg0vfvpk2fqE6mlb4FufwOESpcZ1fRS/DfZ6tv53MukBxCXlkDEP9BgFVTP9ZiIrizBkNO/0QeKah8p0n2LY1jod7LplvVgPTwIRHmh2Pey17XYveste3RrQQPlqXvk/XDPu5Z57uMLt5ME5FDzYi/4YKMvZgsKLzBM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JYqiZOg23W6UB/RFFH+zTXzwzgLltnFIY+l6WdawpiByhKdvB2LGjLFDR7o/lUKx3yzT9EPyKbwjGxdfhIUwg5XMyP1OA8djVvrlzAXazfnA3fsmd0zTAD27ZvsNhF53h19SmZG9IiAOBKLwU+kje7iBwmtwOBNl3GwFaYSlVjo= Received: by 10.114.198.1 with SMTP id v1mr11302940waf.89.1205475580972; Thu, 13 Mar 2008 23:19:40 -0700 (PDT) Received: by 10.114.133.6 with HTTP; Thu, 13 Mar 2008 23:19:40 -0700 (PDT) Message-ID: Date: Fri, 14 Mar 2008 00:19:40 -0600 From: "Scott Marlowe" To: "Jesper Krogh" Subject: Re: Benchmark: Dell/Perc 6, 8 disk RAID 10 Cc: justin , pgsql-performance@postgresql.org In-Reply-To: <47DA1866.3050500@krogh.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <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> <47DA1866.3050500@krogh.cc> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/297 X-Sequence-Number: 29251 On Fri, Mar 14, 2008 at 12:17 AM, Jesper Krogh wrote: > > 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. Is this on a 64 bit or 32 bit machine? We had the problem with a 32 bit linux box (not sure what flavor) just a few months ago. I would not create a filesystem on a partition of 2+TB