X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 91F8756599 for ; Thu, 10 Mar 2005 21:44:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71252-10 for ; Thu, 10 Mar 2005 21:44:52 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by svr1.postgresql.org (Postfix) with ESMTP id 590BF5655C for ; Thu, 10 Mar 2005 21:44:51 +0000 (GMT) Received: by wproxy.gmail.com with SMTP id 70so744534wra for ; Thu, 10 Mar 2005 13:44:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=MaGNO8UKafJ7nf9CYYvGMSEquYRocCJq4cadjd/GpINx1HI3TVwGQ50V0gQ53cC38IMBYxm1gZnUNGLPrPeX/wx63wBXHfnPtBAx4z+AlclaC/FjczXv0Efwi3rC37Wd7/plEJDczd4Nt3S43e3yYN/oPsC4wn8BcZKJ0hPE+jo= Received: by 10.54.84.17 with SMTP id h17mr791191wrb; Thu, 10 Mar 2005 13:44:53 -0800 (PST) Received: by 10.54.18.53 with HTTP; Thu, 10 Mar 2005 13:44:53 -0800 (PST) Message-ID: <33c6269f0503101344397bf803@mail.gmail.com> Date: Thu, 10 Mar 2005 16:44:53 -0500 From: Alex Turner Reply-To: Alex Turner To: PgSQL General List Subject: Fwd: IO Timeout In-Reply-To: <33c6269f050310111892ae175@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <33c6269f050310111892ae175@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.221 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200503/425 X-Sequence-Number: 74741 I have a question about IO timeouts: We are using the 3ware escalade 9500S series of cards, and we had a drive failure this morning. Apparnetly the card waits 30 seconds for the drive to respond, and if it doesn't, it put's the drive in a fail state. Postgres it seems didn't wait 30 seconds before it decided that the system was upset, and put the database in maintainence mode. Is there a way to increase to IO wait timeout so this doesn't happen? Alex Turner netEconomist