From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5FBD2138A1A for ; Tue, 3 Feb 2015 11:29:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 86B4BE0980; Tue, 3 Feb 2015 11:29:46 +0000 (UTC) Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1A9C1E096C for ; Tue, 3 Feb 2015 11:29:45 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id ms9so50538713lab.1 for ; Tue, 03 Feb 2015 03:29:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=uHxvVy7HgMc4SKMQAr5QY5HkZctEqltdmbcXEu0qTOA=; b=uEG6RjKNjdKnwIrOyDkAPnRjdzcRl7dFN1j6DX00UdClorfJ2lhOuPmIOZ+oZDI1HJ i08++Z4mEnkRGM89UGWOOGzWEpwAknCxRuZnBVbs2OSLkZTZNHQXhl8taCY1rlTlyHwb KJSVNUCGisQH7bfxEKKOsMKqMsql6F1RravxrED3v09+er0yjVIJUuEqqD/IZOd5x+vo A4P9ALAj/Y3sGmOoUPiVXbBgVbuk2IacI45vEm8S+cTkXs6kzAWYGZnq0unCJJAZIqw3 K0so5k5E8R3CjJc9QysWgBdRp4N7EaMJEHQINGA73LM+zcexaAgmLiO7TVULfhoXvqES Arww== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.152.9.41 with SMTP id w9mr23369254laa.17.1422962983696; Tue, 03 Feb 2015 03:29:43 -0800 (PST) Received: by 10.152.116.102 with HTTP; Tue, 3 Feb 2015 03:29:43 -0800 (PST) In-Reply-To: References: <20150202003234.1cf5ff91@hal9000.localdomain> Date: Tue, 3 Feb 2015 06:29:43 -0500 Message-ID: Subject: Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1) From: Tom H To: Gentoo User Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 4cd3e9bb-748b-484d-a76c-589aaec5151a X-Archives-Hash: 89e9cd73df586b5d344b6aade9a2d09e On Mon, Feb 2, 2015 at 8:46 PM, walt wrote: > On 02/02/2015 10:29 AM, Tom H wrote: >> On Sun, Feb 1, 2015 at 7:31 PM, walt wrote: >>> >>> For example, I had to add the rpcbind.service to the multi-user >>> systemd target because even nfs3 seems to need it. >> >> You must mean "because especially nfsv3 needs it" because, >> theoretically, nfsv4 doesn't need rpcbind since an nfsv4 mount only >> needs to now about rpc.nfsd's default port 2049. > > This morning I got "waiting on lockfile foo in /usr/portage/distfiles" > "locking not available" from my nfs3 clients when trying to download > needed source files. > > I worked around this failure by using the nfs nolock mount option, and > then I gave up and restored nfs4 to all my kernels and nfs-utils packages. > > I don't recall having this problem back in my former nfs3-only days. > Maybe I've forgotten something obvious that I did back then? There used to be an rpc.lockd daemon but lockd's been moved to a kernel module for nfsv3 and to nfsd for nfsv4. RHEL 5 has it (nfs-utils 1.09) and RHEL 6 doesn't (nfs-utils 1.2) so it must've been dropped with v1.1 or v1.2. I don't know when it was dropped in Gentoo terms (probably 6-7 years ago). Does this ring a bell? Does file locking work for an nfsv3 mount after you re-enable nfsv4 in your kernel config? If yes, then you're missing some kernel config that's being enabled automatically when you enable nfsv4. I can't think of what it might be since AFAIK you can't enable NFS_FS or NFSD without enabling FILE_LOCKING. If no, then are you setting static ports for statd and lockd and allowing access to these ports with iptables?