From owner-freebsd-hackers@freebsd.org Sun Feb 26 14:43:30 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10318CEE369 for ; Sun, 26 Feb 2017 14:43:30 +0000 (UTC) (envelope-from freebsd-hackers@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 963DD7C1 for ; Sun, 26 Feb 2017 14:43:28 +0000 (UTC) (envelope-from freebsd-hackers@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Sun, 26 Feb 2017 15:43:26 +0100 id 00F4BD11.58B2E98E.00013A49 Date: Sun, 26 Feb 2017 15:43:25 +0100 From: Milan Obuch To: Daniel Braniss Cc: Daniel Shahaf , freebsd-hackers@freebsd.org Subject: svn over nfs - was kern.ostype - where gets its value? Message-ID: <20170226154325.48cab161@zeta.dino.sk> In-Reply-To: References: <20170226132548.69223dcd@zeta.dino.sk> <20170226124742.GA10967@fujitsu.shahaf.local2> <20170226140645.5d3ad3c1@zeta.dino.sk> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; i386-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 14:43:30 -0000 On Sun, 26 Feb 2017 16:05:41 +0200 Daniel Braniss wrote: > > On 26 Feb 2017, at 15:06, Milan Obuch > > wrote: > > > > On Sun, 26 Feb 2017 12:47:42 +0000 > > Daniel Shahaf wrote: > > > >> Milan Obuch wrote on Sun, Feb 26, 2017 at 13:25:48 +0100: > >>> From my experience it looks like this problem is caused by svn not > >>> being able to be run on nfs mounted directory, no matter the > >>> architecture - today I tried with both server and client running > >>> 10.3-STABLE on i386, svn just fails. > >> > >> svn can work over nfs provided that locking is supported. > >> > > > > How could I find whether locking is supported/make sure it is? > you need to run rpc_lockd on both server & client > (rpc_lockd_enable=yes in rc.conf) probably also rpc_statd too. > [ snip ] Yes, I found this in FreeBSD handbook too, see URL https://www.freebsd.org/doc/handbook/network-nfs.html, but it does not solve this issue... I make sure both lockd and statd processes are running on both server and client, restarted them and nfsd, mountd, rpcbind couple of times, but while things changed, issue is not yet resolved. Without lockd/statd, svnliteversion on client shows # svnliteversion /usr/src svnversion: E155016: The working copy database at '/usr/src' is corrupt. When lockd/statd are running, it changes to # svnliteversion /usr/src svnversion: E200033: sqlite[S5]: database is locked, executing statement 'PRAGMA case_sensitive_like=1;PRAGMA synchronous=OFF;PRAGMA recursive_triggers=ON;PRAGMA foreign_keys=OFF;PRAGMA locking_mode = NORMAL;PRAGMA journal_mode = TRUNCATE;' and that's it. I will try to checkout fresh svn on server with both lockd/statd running as well, just in case, but I do not expect it will work then. Regards, Milan