Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id C79729FB9FC for ; Wed, 4 Apr 2007 10:36:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 57567-01-3 for ; Wed, 4 Apr 2007 10:36:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 5FE3F9FB8A5 for ; Wed, 4 Apr 2007 10:36:37 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-221-161.bk12-dsl.surnet.cl [201.221.221.161]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l34DaN8I006595; Wed, 4 Apr 2007 06:36:23 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id F2434329EE; Wed, 4 Apr 2007 09:36:20 -0400 (CLT) Date: Wed, 4 Apr 2007 09:36:20 -0400 From: Alvaro Herrera To: Peter Kovacs Cc: Andreas Kostyrka , "david@lang.hm" , Geoff Tolley , Ron , "jason@ohloh.net" , pgsql-performance@postgresql.org Subject: Re: SCSI vs SATA Message-ID: <20070404133620.GD8549@alvh.no-ip.org> Mail-Followup-To: Peter Kovacs , Andreas Kostyrka , "david@lang.hm" , Geoff Tolley , Ron , "jason@ohloh.net" , pgsql-performance@postgresql.org References: <9C0858F5-0A48-4AF9-80FF-E4BA14F0F965@ohloh.net> <4613053F.5070401@polimetrix.com> <20070404124640.GC20893@andi-lap.la.revver.com> <20070404131920.GA8549@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.88.5/2987/Sat Mar 31 20:15:28 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 04 Apr 2007 06:36:24 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/64 X-Sequence-Number: 23941 Peter Kovacs escribió: > But if an individual disk fails in a disk array, sooner than later you > would want to purchase a new fitting disk, walk/drive to the location > of the disk array, replace the broken disk in the array and activate > the new disk. Is this correct? Ideally you would have a spare disk to let the array controller replace the broken one as soon as it breaks, but yeah, that would be more or less the procedure. There is a way to defer the walk/drive until a more convenient opportunity presents. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.