[Bug 241577] F_SETLK on NFS

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241577

            Bug ID: 241577
           Summary: F_SETLK on NFS
           Product: Base System
           Version: 11.3-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: mi at FreeBSD.org

I'm forced to use an NFS-share as home directory for a while. The mount is
using default options -- nothing fancy:

         narawntapu:/green/home  /home    nfs     rw  0 0

However, various things (browsers, Thunderbird) aren't working -- manifesting
all sorts of very strange problems.

Apparently, the underlying reason is the same for all of them -- SQLite3 can
not operate on its database-files, which are used for much of the software's
configuration nowadays.

A very simple test-case is:

        % echo .databases | sqlite3 ~/meow.db
        Error: disk I/O error

Using /tmp -- or any other local filesystem instead of ~/ -- works as expected.

I used ktrace to see, what exactly is failing in sqlite3, and found this:

 43469 sqlite3  CALL  fcntl(0x3,F_SETLK,0x7fffffffb920)
 43469 sqlite3  RET   fcntl -1 errno 45 Operation not supported
 43469 sqlite3  CALL  write(0x2,0x7fffffffc8c0,0x16)
 43469 sqlite3  GIO   fd 2 wrote 22 bytes
       "Error: disk I/O error

The NFS-server (narawntapu) has lock-daemon running:
   PID TT  STAT    TIME COMMAND
   785  -  Ss   0:02,00 /usr/sbin/rpc.lockd

Neither the client nor the server have any kernel messages in the logs relating
to this problem.

Why is not F_SETLK working? I'm not expecting high performance, but I expect it
to work...

-- 
You are receiving this mail because:
You are the assignee for the bug.