From owner-freebsd-stable@freebsd.org Wed Aug 21 02:59:52 2019 Return-Path: Delivered-To: freebsd-stable@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 41C0AE7AE1 for ; Wed, 21 Aug 2019 02:59:52 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (flets-sg1026.kamome.or.jp [202.216.24.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp", Issuer "smtp" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46CspG3n8Xz4Npn for ; Wed, 21 Aug 2019 02:59:49 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (kx.truefc.org [202.216.24.26]) by kx.truefc.org (8.15.2/8.15.2) with ESMTP id x7L2xcVY044629; Wed, 21 Aug 2019 11:59:38 +0900 (JST) (envelope-from kiri@kx.truefc.org) Message-Id: <201908210259.x7L2xcVY044629@kx.truefc.org> Date: Wed, 21 Aug 2019 11:59:38 +0900 From: KIRIYAMA Kazuhiko To: Peter Jeremy Cc: Trond =?ISO-8859-1?Q?Endrest=F8l?= , KIRIYAMA Kazuhiko , "FreeBSD-stable@FreeBSD.org" Subject: Re: `uname -a' can't display revision In-Reply-To: <20190820194909.GA75146@server.rulingia.com> References: <201908200200.x7K20gxg003413@kx.truefc.org> <201908201118.x7KBIhCD027716@kx.truefc.org> <201908201224.x7KCO5rh030491@kx.truefc.org> <20190820194909.GA75146@server.rulingia.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 MULE XEmacs/21.4 (patch 24) (Standard C) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 46CspG3n8Xz4Npn X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of kiri@truefc.org has no SPF policy when checking 202.216.24.26) smtp.mailfrom=kiri@truefc.org X-Spamd-Result: default: False [0.02 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.24)[-0.240,0]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[truefc.org]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.59)[-0.594,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.25)[-0.245,0]; R_SPF_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4704, ipnet:202.216.0.0/19, country:JP]; IP_SCORE(-0.01)[country: JP(-0.03)]; ONCE_RECEIVED(0.10)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 02:59:52 -0000 On Wed, 21 Aug 2019 04:49:09 +0900, Peter Jeremy wrote: >=20 > [1 ] > On 2019-Aug-20 14:36:14 +0200, Trond Endrest=F8l wrote: > >Maybe NFS is to blame, particularly if file locks cannot be obtained. >=20 > Yes, it is. SVN tries to obtain locks, even for read-only commands like > "svn info". My solution is to mount /usr/src with the option "nolockd". That it is! Add nolockd option to fstab and `uname -a' put fine: admin@tbedfs:~ % uname -a FreeBSD tbedfs 12.0-STABLE FreeBSD 12.0-STABLE #0 r351318: Wed Aug 21 11:06= :40 JST 2019 root@tbedfs:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 admin@tbedfs:~ % cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/vtbd0p2 / ufs rw 1 1 /dev/vtbd0p3 none swap sw 0 0 vm.tfc:/.dake /.dake nfs rw 0 0 vm.tfc:/ds/src/stable/12/r351318 /usr/src nfs ro,nolockd = 0 0 vm.tfc:/ds/obj/stable/12/r351318 /usr/obj nfs rw 0 = 0 admin@tbedfs:~ %=20 Thanks for your help! --- KIRIYAMA Kazuhiko >=20 > --=20 > Peter Jeremy > [2 signature.asc ] >=20