[Xapian-discuss] Flint Database 'Can't acquire write lock'?
Josef Novak
josef.robert.novak at gmail.com
Sat Apr 21 06:03:49 BST 2007
Hi,
I tried to do some checking up on my filesystem:
stat -f ./
File: "./"
ID: 0 Namelen: 255 Type: nfs
Blocks: Total: 127995985 Free: 7138492 Available: 7138492 Size: 8192
Inodes: Total: 4294967295 Free: 4294967295
I see an /usr/sbin/rpc.nfsd command and a 'lockfile' which is in my
path. I cannot seem to locate a 'lockd' command. So perhaps that is
the problem.
joe
On 4/20/07, Olly Betts <olly at survex.com> wrote:
> On Fri, Apr 20, 2007 at 06:37:47PM +0900, Josef Novak wrote:
> > I'm using xapian-core-0.9.9, built on a 64bit linux machine
> > (Linux 2.4.21-143-smp x86_64 unknown ), employing a bash shell.
>
> Flint relies on fcntl() for locking, so perhaps the filing system
> you have the database on doesn't support this. What is the filing
> system? If it's NFS, make sure you're running 'lockd'.
>
> Quartz uses completely different locking technique which works on
> NFS without lockd, but it leaves a stale lock behind if the process
> exits unexpectedly, which is annoying.
>
> If it's not obviously the FS, can you try a snapshot tarball of SVN
> HEAD? There are have been some minor tweaks to the locking code:
>
> http://www.oligarchy.co.uk/xapian/trunk/
>
> Cheers,
> Olly
>
More information about the Xapian-discuss
mailing list