Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id B5F8E1335ED4 for ; Mon, 20 Sep 2010 15:15:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 90961-01 for ; Mon, 20 Sep 2010 18:15:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 433D51335BA8 for ; Mon, 20 Sep 2010 15:15:45 -0300 (ADT) Received: from [192.168.1.6] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0M4klp-1OcXDv04Fh-00ytIE; Mon, 20 Sep 2010 20:15:42 +0200 Message-ID: <4C97A4CB.6050604@2ndquadrant.com> Date: Mon, 20 Sep 2010 14:15:39 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: dbhandary@iii.com CC: pgsql-admin@postgresql.org Subject: Re: files under pg_clog directories are missing References: <4C940889.3000505@iii.com> <4C9432DA.4000609@2ndquadrant.com> <4C9785B6.6030506@iii.com> In-Reply-To: <4C9785B6.6030506@iii.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:AqXmCuIua5QrxLdFswvwecsbE6/c1B4Hos28plRy0Je cHikxRhwVA86JfF1Ot9G5ji8n7LbeczvtuE88bJKqpJuwOG9wD dc271AHQYbQhGOko5BnqblJPDToxVHKMZByrWOo5HQzl5dMwUA MWgtNpkHDqMUJDfH9rHQAAprL+epK22lUfdBO9mGk4DGG986pN 5X1TCPrGQVwKDEPlPVIcX1JoD6CmiQUpV1KwzkVdFw= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201009/121 X-Sequence-Number: 35665 Dinesh Bhandary wrote: > As for the nature of the corruption I still do know know what kind of > hardware problems led to this; it happened at one of our clients site > and we are still waiting to find out what caused it. One piece of > info we got was postgres data directory turned into read only partition. That can happen when a major disk-level problem occurs; system remounts as read-only because it doesn't think it can safely write to it anymore. I'd check into the system kernel logs as soon as possible, to try and find a disk error that kicked the whole thing off. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance" Pre-ordering at: https://www.packtpub.com/postgresql-9-0-high-performance/book