Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5C4F4637265 for ; Fri, 20 Feb 2009 12:03:24 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 10259-04 for ; Fri, 20 Feb 2009 12:03:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from is.rice.edu (is.rice.edu [128.42.42.24]) by mail.postgresql.org (Postfix) with ESMTP id 27D7B637261 for ; Fri, 20 Feb 2009 12:03:16 -0400 (AST) Received: from scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) by is.rice.edu (Postfix) with ESMTP id 95CFD41820; Fri, 20 Feb 2009 10:03:14 -0600 (CST) Received: from is.rice.edu ([128.42.42.24]) by scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) (amavisd-new, port 10024) with ESMTP id 02533-04; Fri, 20 Feb 2009 10:03:13 -0600 (CST) Received: by is.rice.edu (Postfix, from userid 18612) id DB2E741819; Fri, 20 Feb 2009 10:03:13 -0600 (CST) Date: Fri, 20 Feb 2009 10:03:13 -0600 From: Kenneth Marshall To: Nicola Mauri Cc: pgsql-admin@postgresql.org Subject: Re: Crash with data corruption under Windows Message-ID: <20090220160313.GL14957@it.is.rice.edu> References: <499EBEF0.1010408@saga.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <499EBEF0.1010408@saga.it> User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: by amavis-2.2.1 at scan1.mail.rice.edu X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/155 X-Sequence-Number: 31376 On Fri, Feb 20, 2009 at 03:32:16PM +0100, Nicola Mauri wrote: > > We run into the following issue with Windows 2003 and Postgres 8.2.6 while > database was running: > > FATAL: "pg_tblspc/16405/37638" is not a valid data directory > DETAIL: File "pg_tblspc/16405/37638/PG_VERSION" is missing. > ERROR: could not open relation 16405/37638/2661: No such file or > directory > ERROR: could not open relation 16405/37638/2659: No such file or > directory > ERROR: could not write block 4 of relation 16405/37638/37656: Permission > denied > CONTEXT: writing block 4 of relation 16405/37638/37656 > ... > WARNING: could not write block 4 of 16405/37638/37656 > DETAIL: Multiple failures --- write error may be permanent. > > This happened 4 times in the last few months! Usually after the crash > datafiles appear to be corrupted, but in some other cases they completely > disappear from the filesystem (tablespace directory is empty) and we have > to recreate the entire db from the last dump. > > No suspicious activities have been detected on the server (unauthorized > accesses, anti-virus intervention) and information about disappeared files > cannot be found using an undelete utilities. Disk hardware is healthy and > no other part of the filesystem seems to be affected by such strange > deletions (several applications, including an oracle database, are > correctly running on the server). > > Since the problem seems involving only directories containing tablespaces > (stored on local partition E:\) we are pointing our attention to "Reparse > Point" and "NTFS Junction" mechanism. > > Could be there issues in those features? > > Thanks in advance, > Nicola Mauri > I did not check the release note, but you do realize that you are 6 releases back from the latest stable 8.2 version. Maybe an upgrade would help. Cheers, Ken