Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 601E62E005B for ; Thu, 17 Apr 2008 13:09:05 -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 82427-02 for ; Thu, 17 Apr 2008 13:08:58 -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.180]) by developer.postgresql.org (Postfix) with ESMTP id C23402E0052 for ; Thu, 17 Apr 2008 13:08:58 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n7so207628wag.5 for ; Thu, 17 Apr 2008 09:08:55 -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=av9+3mHIy/t2nFlTht8K6yoMoYe5LexaEJt/af8fPO8=; b=qhQ8nPJ7rCpo8z0vPO1SC+nUTmzKHnvmNobGzOj/wcZpjKkpW5UwbUfum/oew4VINxDT/y4Fr+IVyi8DmjdEDlLA3iuaWAXag0CZZzGWa01WiSWS6ecBBHcqDbgcbAjg0TK94XDpMzVwtjXG8gVMsntMIBQiT+QgfVrJtri2SO8= 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=rbGzNduluHSRCT1nvt//c043zmhqEkc1RiajGExiB3E13Azl3OTfHk9aiWIV+3RKsHNrJqLwNatH9yUnrgXzGtsH/Jt7Y3jYMMUG/wyUKtE9XtMkuUvizEo4A7gAe9M/+JC8GihLq4ySBSACrd5Oc9rMgCmMm7uaZm2mKbop8XQ= Received: by 10.115.79.8 with SMTP id g8mr1631460wal.215.1208448535687; Thu, 17 Apr 2008 09:08:55 -0700 (PDT) Received: by 10.114.102.14 with HTTP; Thu, 17 Apr 2008 09:08:55 -0700 (PDT) Message-ID: <2ca799770804170908t26cf4237qee7af185b70a29c2@mail.gmail.com> Date: Thu, 17 Apr 2008 19:08:55 +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: <20825.1208448367@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1730_28998372.1208448535607" 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> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/177 X-Sequence-Number: 28941 ------=_Part_1730_28998372.1208448535607 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. Hmm didn't think of that, will do that asap (tomorrow). Thanks for your help. Regards Mikko ------=_Part_1730_28998372.1208448535607 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

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.

Hmm didn't think of that, will do that asap (tomorrow). Thanks for your help.

Regards

Mikko

------=_Part_1730_28998372.1208448535607--