From owner-freebsd-bugs@freebsd.org Tue Oct 29 21:26:22 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DD601164FFC for ; Tue, 29 Oct 2019 21:26:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 472l5B5Zrpz45JN for ; Tue, 29 Oct 2019 21:26:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id BDCB1164FFB; Tue, 29 Oct 2019 21:26:22 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD8C1164FFA for ; Tue, 29 Oct 2019 21:26:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 472l5B4cYjz45JM for ; Tue, 29 Oct 2019 21:26:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 82E2D27FD3 for ; Tue, 29 Oct 2019 21:26:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9TLQMC4027093 for ; Tue, 29 Oct 2019 21:26:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9TLQM5g027083 for bugs@FreeBSD.org; Tue, 29 Oct 2019 21:26:22 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241577] F_SETLK on NFS Date: Tue, 29 Oct 2019 21:26:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mi@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 21:26:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241577 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@FreeBSD.org Reporter: mi@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 -- manifesti= ng 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 expec= ted. 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 rela= ting to this problem. Why is not F_SETLK working? I'm not expecting high performance, but I expec= t it to work... --=20 You are receiving this mail because: You are the assignee for the bug.=