Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id E09D62E0073 for ; Tue, 22 Apr 2008 01:35:49 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 36227-03 for ; Tue, 22 Apr 2008 01:35:24 -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 developer.postgresql.org (Postfix) with ESMTP id D3E922E0067 for ; Tue, 22 Apr 2008 01:34:45 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n7so3603390wag.5 for ; Mon, 21 Apr 2008 21:34:44 -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:references; bh=VbBikim+18Bzg4Db47xf+vuU8eHIwU1bzSDBMoTTAEc=; b=nh4T9bObbXXngSLC4KeSYwcd8rR5pUQZUIlETDvSCMGPluenSolrW4Zi6bv4GQi4R1G7z7tDYAJYQCdOSf+32flj6/cdLv/IKWv19rw892OHiYGbSA0ShK66vNNaqz4xbs3W4NEGo9lrFnN9e2vvP593sLDaPYfQyS2P4M0Ysd0= 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:references; b=vRACyx9wGa19GPybQqULVHMlPZEDmz9PgOH8wfHraSZJ5dJf8MWG8X++UY9UdbsUvVP02V3I1HU2DQFhvvEKCmBKw2m9oZ4x6VC/G/FiSq+Eyb3eiZSzYm4PNkOvjkJtdR84dT2wtMjPhpoeNPWKgAEJkS14bujTgfysowv3BhY= Received: by 10.114.53.18 with SMTP id b18mr6910441waa.220.1208838884159; Mon, 21 Apr 2008 21:34:44 -0700 (PDT) Received: by 10.114.95.13 with HTTP; Mon, 21 Apr 2008 21:34:44 -0700 (PDT) Message-ID: <2ca799770804212134x2398fe22u2f1a732d5e04c50b@mail.gmail.com> Date: Tue, 22 Apr 2008 07:34:44 +0300 From: "Mikko Partio" To: "Tom Lane" Subject: Re: FATAL: could not open relation xxx: No such file or directory Cc: "Pavan Deolasee" , pgsql-admin@postgresql.org In-Reply-To: <2ca799770804170908t26cf4237qee7af185b70a29c2@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6952_734968.1208838884151" References: <2ca799770804090647m759b72f9gf2d49b4bf7cc8bdf@mail.gmail.com> <2ca799770804142336q6422af38me80054c82699d1e2@mail.gmail.com> <2ca799770804170308m367eaea2nc7899198c0b260e0@mail.gmail.com> <2e78013d0804170336j4299161bm3f280fc9b930b474@mail.gmail.com> <2ca799770804170344o65291ce3pa56a2694f7a15bc5@mail.gmail.com> <20021.1208445022@sss.pgh.pa.us> <2ca799770804170859t39a5532x4629953e0ec3a600@mail.gmail.com> <20825.1208448367@sss.pgh.pa.us> <2ca799770804170908t26cf4237qee7af185b70a29c2@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/216 X-Sequence-Number: 28980 ------=_Part_6952_734968.1208838884151 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Apr 17, 2008 at 7:08 PM, Mikko Partio wrote: > > > On Thu, Apr 17, 2008 at 7:06 PM, Tom Lane wrote: > > > "Mikko Partio" writes: > > > On Thu, Apr 17, 2008 at 6:10 PM, Tom Lane wrote: > > >> I think you've got really serious filesystem-level problems. Have > > you > > >> tried running any hardware diagnostics? Are you sure you're using a > > >> stable kernel version? > > > > > I run fsck on the filesystem (gfs) -- no problems found. The disks are > > from > > > a san and the diagnostic programs say there's nothing wrong. I also > > have > > > other db clusters running on different filesystems (also gfs) and I > > have > > > never had any problems with them. > > > > Some RAM checks wouldn't be out of place either. > > Memtest86+ has now been running for 20+ hours and no errors has been found. I was also unable to reproduce this problem, but it only happened after a few days of constant activity anyway so I guess it's not so easy to replicate. Any other pointers where to look at? Your help is well appreciated. Regards Mikko ------=_Part_6952_734968.1208838884151 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Thu, Apr 17, 2008 at 7:08 PM, Mikko Partio <mpartio@gmail.com> wrote:


On Thu, Apr 17, 2008 at 7:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Mikko Partio" <mpartio@gmail.com> writes:
> On Thu, Apr 17, 2008 at 6:10 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think you've got really serious filesystem-level problems.  Have you
>> tried running any hardware diagnostics?  Are you sure you're using a
>> stable kernel version?

> I run fsck on the filesystem (gfs) -- no problems found. The disks are from
> a san and the diagnostic programs say there's nothing wrong. I also have
> other db clusters running on different filesystems (also gfs) and I have
> never had any problems with them.

Some RAM checks wouldn't be out of place either.


Memtest86+ has now been running for 20+ hours and no errors has been found. I was also unable to reproduce this problem, but it only happened after a few days of constant activity anyway so I guess it's not so easy to replicate. Any other pointers where to look at? Your help is well appreciated.

Regards

Mikko

------=_Part_6952_734968.1208838884151--