Re: could not read transaction log directory ...?

Do you have any options for NFS set in your fstab for this share?  We had 
to make a few changes to get NFS to work reliably (we still don't use it 
for database, just raw text files and such.)  My options are:

timeo=10,retry=1,bg,soft,intr,rsize=8192,wsize=8192

If anyone has any suggestions to make to mine feel free, those are the 
settings I got from one of the networking guys, they may well be 
non-optimal.  But NFS doesn't just disappear for seconds at a time anymore 
like it used to during snapshots.
On Thu, 8 May 2003, Michael 
Brusser wrote:

> I don't have much choice here - these are development and
> test machines, few different platforms but all on NFS.
> Testing is very intensive and Postgres takes up a lot of beating.
> I think this is the first time we ran into this kind of problem.
> 
> I just want to thank everyone for help.
> Mike.
> 
> 
> > -----Original Message-----
> > From: Christopher Kings-Lynne [mailto:chriskl@familyhealth.com.au]
> > Sent: Thursday, May 08, 2003 10:16 PM
> > To: michael@synchronicity.com; Christopher Browne
> > Cc: pgsql-hackers@postgresql.org
> > Subject: Re: [HACKERS] could not read transaction log directory ...?
> >
> >
> > > Does this mean that you are storing your filesystems on NFS?
> > >
> > > That could well be the root of the problem; NFS has been somewhat in
> > > flux, and is usually not a highly recommended way of storing PG data.
> > >
> > > I hear D'Arcy Cain uses NFS fairly successfully for the purpose, but I
> > > believe he's using NetApp boxes, which are _quite_ different from the
> > > norm, and likely aren't what you are using.
> > >
> > > My first suggestion would be Stop Using NFS (unless you are really quite
> > > certain of what you're doing).
> >
> > Or switch to FreeBSD - ever since the 'fsx' NFS automatic testing
> > tool came
> > out from Apple, FreeBSD has had an excellent NFS implementation.
> >
> > Chris
> >
> >
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>