Re: could not read transaction log directory ...? - Mailing list pgsql-hackers

From Michael Brusser
Subject Re: could not read transaction log directory ...?
Date
Msg-id DEEIJKLFNJGBEMBLBAHCAEEDDCAA.michael@synchronicity.com
Whole thread Raw
In response to Re: could not read transaction log directory ...?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: could not read transaction log directory ...?
Re: could not read transaction log directory ...?
List pgsql-hackers
From errno.h :
... ...
/* Defined for the NFSv3 protocol */
#define EBADHANDLE      521     /* Illegal NFS file handle */
#define ENOTSYNC        522     /* Update synchronization mismatch */
#define EBADCOOKIE      523     /* Cookie is stale */
... ...

"Cookie is stale" - ..? 
Should I consider some problems with the file server?
The strange thing is that process always crashes some 30 minutes
after start. Another point is that it works fine on another machine -
Red Hat 7.2 with 2.4.9 kernel.

I'm not sure what to make out of this.
Thanks,
Mike.


> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Thursday, May 08, 2003 12:25 AM
> To: michael@synchronicity.com
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] could not read transaction log directory ...?
> 
> 
> Michael Brusser <michael@synchronicity.com> writes:
> > 2003-05-07 15:04:10 PANIC:  could not read transaction log directory -
> >                            (<my_dir_path>/pg_xlog): Unknown error 523
> 
> Bizarre.  Can you dig around in your kernel sources and see what errno
> 523 might mean?
> 
>             regards, tom lane
> 



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: CIDR in pg_hba.conf
Next
From: Luis Sousa
Date:
Subject: (no subject)