Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 7C5351337B93 for ; Wed, 4 May 2011 17:14:06 -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 08072-05-4 for ; Wed, 4 May 2011 20:13:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.virtall.com (mail.virtall.com [178.63.195.102]) by mail.postgresql.org (Postfix) with ESMTP id 31ADC1337B4E for ; Wed, 4 May 2011 17:13:48 -0300 (ADT) Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 9D0A33624FE; Wed, 4 May 2011 22:13:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=wpkg.org; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=default; bh=ml06NcC8E 08XtBRxwKCQ7lcK23U=; b=sutEjfzhMMtuORGERDmSg6Qe0iMkC+ipN5KoYOnTu OW+iLGEDP+oTmopqhTDcPokTxwLJyQ6VEO317rKflPAq51ggewlaJNIwJ4watbF5 lk8xsd9ysWnXudQeoPYigdYFgJhobKlUQdrZ5pizlS5z/id322uEoPtYVmNdgz9q Ko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=wpkg.org; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=default; b=jaJ hF3TAmp27qOlYHtZ01sbfZDgnp0M9u0bkITc9bai8BqzWr6D7lAUQ58iX/ejYEWC sq5OSkYQDqFBk1ayIYizvP0KspDdmi+XLin8/+W40xdCXk1yOWMy1UwbsIn4Svan 9ZB12G0zfKOmgGNjvj5cxZ9JDouuX3snAMys2/qw= Received: from [192.168.10.145] (e183095092.adsl.alicedsl.de [85.183.95.92]) by mail.virtall.com (Postfix) with ESMTPSA id EB4BD36225B; Wed, 4 May 2011 22:13:45 +0200 (CEST) Message-ID: <4DC1B378.6050105@wpkg.org> Date: Wed, 04 May 2011 22:13:44 +0200 From: Tomasz Chmielewski User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110419 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Scott Marlowe CC: Kevin Grittner , pgsql-admin@postgresql.org Subject: Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now? References: <4DC0F063.70306@wpkg.org> <4DC15137020000250003D295@gw.wicourts.gov> <4DC19CD1.7070600@wpkg.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 X-Spam-Level: X-Archive-Number: 201105/52 X-Sequence-Number: 37489 On 04.05.2011 21:50, Scott Marlowe wrote: > Then another pg_clog file disappeared. > > Is it possible there's some rogue process deleting files in pg_clog > somehow? I don't think. > Have you run an fsck on this drive to make sure it's not got > any file system errors? Also, don't think there is any corruption here. AFAIR, this system never crashed. Could be there is some silent corruption though - but if there really was one, we would likely see the kernel complaining, stale files elsewhere, and so on. Without such clues on filesystem corruption, I can't afford downtime. I didn't mention, but the application first talks to pgpool, which talks to two database servers (i.e. inserts to both). The real fun begins here - this is from two different servers: db10:/var/log/postgresql# zgrep "No such" * postgresql_log:May 4 18:24:28 db10 postgres[15751]: [23-2] 2011-05-04 18:24:28 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. postgresql_log:May 4 22:43:44 db10 postgres[15773]: [555-2] 2011-05-04 22:43:44 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. postgresql_log:May 4 22:44:30 db10 postgres[15791]: [1841-2] 2011-05-04 22:44:30 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. postgresql_log:May 4 22:55:53 db10 postgres[15741]: [4114-2] 2011-05-04 22:55:53 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. db20:/var/log/postgresql# zgrep "No such" * postgresql_log:May 4 18:24:28 db20 postgres[27114]: [2-2] 2011-05-04 18:24:28 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. postgresql_log:May 4 22:43:44 db20 postgres[27116]: [2-2] 2011-05-04 22:43:44 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. postgresql_log:May 4 22:44:30 db20 postgres[27138]: [2-2] 2011-05-04 22:44:30 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. postgresql_log:May 4 22:55:53 db20 postgres[27104]: [2-2] 2011-05-04 22:55:53 SGT DETAIL: Could not open file "pg_clog/0601": No such file or directory. I can't exclude some corruption happened much earlier on db10; the whole database (as binary files) was copied to db20 almost 2 months ago. Why would it start showing pg_clog files missing just 2 days ago, and not earlier? Hmm. -- Tomasz Chmielewski http://wpkg.org