On Fri, 2002-06-07 at 20:16, John Jetmore wrote:
> This seems like an issue to me as our db directory is on NFS (a netapp
> F760). In fact, the whole spool directory is on NFS, and has for the most
> part worked beautifully. We have experienced in the past w/ flock times
> where files on NFS will become unlockable - that is, not only does locking
> not work, but it sort of permanently "freezes out" all locks on that
> inode. fcntl in this case certainly appears to be doing the same thing,
> which explains why removing the files (and thus generating new inodes)
> works here. I had thought that problems like this were why exim
> supported lockfiles so much, but I see in the book that it actually had
> something to do with the size of the file reported by the NFS server. I
> suppose if this is the reason lockfile wouldn't be viewed as necessary
> because the file that gets locked contains no data itself.
This is definitely your problem. Frankly locking on NFS still does not
work 100% reliably after 20 years of development!
Move your db directories onto local disk. They are not valuable data so
if the server goes you have lost nothing, the bandwidth, latency and
reliablity improvements are well worth the change.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham@??? ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
