Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 121E96374B0
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri, 20 Feb 2009 12:14:16 -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 21477-07-2
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri, 20 Feb 2009 12:14:11 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-gx0-f176.google.com (mail-gx0-f176.google.com
	[209.85.217.176])
	by mail.postgresql.org (Postfix) with ESMTP id 503F86374B5
	for <pgsql-admin@postgresql.org>; Fri, 20 Feb 2009 12:14:10 -0400 (AST)
Received: by mail-gx0-f176.google.com with SMTP id 24so3286532gxk.19
	for <pgsql-admin@postgresql.org>; Fri, 20 Feb 2009 08:14:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=7DBeqO+xKpTzAabDsRbjvyfe2Wmf5YKdCU2AASCNkdY=;
	b=FbRpbaK1BIbMo7+nygueQ2O9zceUQLubFrMqfYOVygF9Gm9EZ1xMkoOFcLuU6daSoN
	LA40Zjw//+yqFJcNPBKetJwIo0Ah2wppcj3GyEg/Grkib/NE0ZMyliv6Z88QzLkc1G3u
	AgJWFyTitnvMunPK2HFdOmJu0sHgmTwEOT71I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=mMLqMZ03s4py6SY3a92t0771B8UMZX9GzocGqXfEoCEbNc9yoD00Poi84/XjvJnGpE
	VaOhCzLgNQycwOPi2Gm2GCVEYWBR8yop7V5oFSw6tAacKzxuBKna7H7e50/Fs4Kunk2C
	+ikPVALo2VvGDqHBzovxGK4mDWjFTjS0zpI5Y=
MIME-Version: 1.0
Received: by 10.151.114.13 with SMTP id r13mr2153289ybm.207.1235146449865;
	Fri, 20 Feb 2009 08:14:09 -0800 (PST)
In-Reply-To: <499EBEF0.1010408@saga.it>
References: <499EBEF0.1010408@saga.it>
Date: Fri, 20 Feb 2009 09:14:09 -0700
Message-ID: <dcc563d10902200814l6c43566fkc1ea70ceb93631a1@mail.gmail.com>
Subject: Re: Crash with data corruption under Windows
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Nicola Mauri <nicola.mauri@saga.it>
Cc: pgsql-admin@postgresql.org
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=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200902/156
X-Sequence-Number: 31377

On Fri, Feb 20, 2009 at 7:32 AM, Nicola Mauri <nicola.mauri@saga.it> 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

Usually when I see the permission denied thing there's anti-virus
software hard locking pgsql files in the middle of the day.