[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#551702: kfreebsd-image-7.2-1-486: nfs locking not functional



Package: kfreebsd-image-7.2-1-486
Version: 7.2-9
Severity: important
Tags: kfreebsd

The attached program fails when running over NFS:

$ ./a.out 
lock failed, errno: 45

errno 45 is:

     [EOPNOTSUPP]       The argument fd refers to an object that does
     not support file locking.

The server supports locking:

debian:/home/anarcat# rpcinfo -p 192.168.0.5 | grep lock
    100021    1   udp  56587  nlockmgr
    100021    3   udp  56587  nlockmgr
    100021    4   udp  56587  nlockmgr
    100021    1   tcp  57511  nlockmgr
    100021    3   tcp  57511  nlockmgr
    100021    4   tcp  57511  nlockmgr

I understand that locking over NFS is edgy at best, but it used to work
fine here.

This breaks gmpc and iceweasel. The first aborts coldly with:

MetaDataCache-ERROR **: Failed to create metadata table: disk I/O error
aborting...

ktracing this produces:

  4453 gmpc     CALL  fcntl(0x8,0x8,0xbfbfdc9c)
  4453 gmpc     RET   fcntl -1 errno 45 Operation not supported

which is consistent with the test program.

Iceweasel yields wild warnings about places and history files being used
by another process. The address bar is also unuseable so visiting
websites is challenging.

This doesn't occur when this workstation runs Lenny GNU/Linux.

A.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i686)

Kernel: kFreeBSD 7.2-1-486
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kfreebsd-image-7.2-1-486 depends on:
ii  freebsd-utils                 7.2-8      FreeBSD utilities needed for GNU/k
ii  kldutils                      7.2-8      tools for managing kFreeBSD module

kfreebsd-image-7.2-1-486 recommends no packages.

kfreebsd-image-7.2-1-486 suggests no packages.

-- no debconf information



Reply to: