Re: BUG #2712: could not fsync segment: Permission denied

in verbose mode, the log shows a little bit more:

2006-10-23 03:23:14 LOG:  42501: could not fsync segment 0 of relation
1663/3964774/6411190: Permission denied
2006-10-23 03:23:14 LOCATION:  mdsync, md.c:785
2006-10-23 03:23:14 ERROR:  XX000: storage sync failed on magnetic disk:
Permission denied
2006-10-23 03:23:14 LOCATION:  smgrsync, smgr.c:888

- thomas

----- Original Message -----
From: "Thomas H" <me@alternize.com>
To: <pgsql-bugs@postgresql.org>
Sent: Monday, October 23, 2006 1:28 AM
Subject: [BUGS] BUG #2712: could not fsync segment: Permission denied


>
> The following bug has been logged online:
>
> Bug reference:      2712
> Logged by:          Thomas H
> Email address:      me@alternize.com
> PostgreSQL version: 8.2b1
> Operating system:   windows 2003 standard
> Description:        could not fsync segment: Permission denied
> Details:
>
> sometimes we're seeing loads of errors in the log:
>
> 2006-10-22 23:48:50 LOG:  could not fsync segment 0 of relation
> 1663/3964774/6409340: Permission denied
> 2006-10-22 23:48:50 ERROR:  storage sync failed on magnetic disk:
> Permission
> denied
> 2006-10-22 23:48:51 LOG:  could not fsync segment 0 of relation
> 1663/3964774/6409340: Permission denied
> 2006-10-22 23:48:51 ERROR:  storage sync failed on magnetic disk:
> Permission
> denied
> 2006-10-22 23:48:52 LOG:  could not fsync segment 0 of relation
> 1663/3964774/6409340: Permission denied
> 2006-10-22 23:48:52 ERROR:  storage sync failed on magnetic disk:
> Permission
> denied
> 2006-10-22 23:48:53 LOG:  could not fsync segment 0 of relation
> 1663/3964774/6409340: Permission denied
> 2006-10-22 23:48:53 ERROR:  storage sync failed on magnetic disk:
> Permission
> denied
> {...}
>
> when this happens, there are also files locked within the
> data\base\{dbid}\.
> access to those files are denied by the os - the files vanish as soon as
> postmaster ist stopped & restarted.
>
> i haven't yet found a possible reason - i suspect the error to appear
> *sometimes* after issuing a "VACUUM FULL ANALYZE {tablename}" / "REINDEX
> TABLE {tablename}".
>
> the hardware is checked and ok.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>