1 |
On Tue, Feb 3, 2015 at 7:05 PM, walt <w41ter@×××××.com> wrote: |
2 |
> On 02/03/2015 03:29 AM, Tom H wrote: |
3 |
>> On Mon, Feb 2, 2015 at 8:46 PM, walt <w41ter@×××××.com> wrote: |
4 |
>>> |
5 |
>>> This morning I got "waiting on lockfile foo in /usr/portage/distfiles" |
6 |
>>> "locking not available" from my nfs3 clients when trying to download |
7 |
>>> needed source files. |
8 |
> |
9 |
>>> I don't recall having this problem back in my former nfs3-only days. |
10 |
>>> Maybe I've forgotten something obvious that I did back then? |
11 |
>> |
12 |
>> There used to be an rpc.lockd daemon but lockd's been moved to a |
13 |
>> kernel module for nfsv3 and to nfsd for nfsv4. RHEL 5 has it |
14 |
>> (nfs-utils 1.09) and RHEL 6 doesn't (nfs-utils 1.2) so it must've been |
15 |
>> dropped with v1.1 or v1.2. I don't know when it was dropped in Gentoo |
16 |
>> terms (probably 6-7 years ago). Does this ring a bell? |
17 |
> |
18 |
> Yes, I remember rpc.lockd. |
19 |
> |
20 |
>> Does file locking work for an nfsv3 mount after you re-enable nfsv4 in |
21 |
>> your kernel config? |
22 |
> |
23 |
> Hm. No, I still get the same "No locks available" error. |
24 |
> |
25 |
>> If no, then are you setting static ports for statd and lockd and |
26 |
>> allowing access to these ports with iptables? |
27 |
> |
28 |
> Noooo, that's way above my pay grade :) |
29 |
> |
30 |
> I mentioned earlier in this thread that, when I run this command: |
31 |
> |
32 |
> #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 |
33 |
> |
34 |
> it hangs indefinitely, but if I hit Ctrl-c and quickly re-run the same |
35 |
> command it succeeds. (I've been trying to measure what "quickly" means |
36 |
> but it seems to vary, seems random, but always less than a minute.) |
37 |
|
38 |
I now remember you saying earlier. Sorry. |
39 |
|
40 |
I can't think of how or why! |
41 |
|
42 |
Does using "mount -v ..." show different outputs for the failing and |
43 |
successful mounts? |
44 |
|
45 |
|
46 |
> I'm posting this info mainly for the benefit of future googlers because |
47 |
> nfs4 is working well and I don't really *need* nfs3. |
48 |
> |
49 |
> If you're interested in this problem I'd be happy to try any/all debugging |
50 |
> experiments, but otherwise don't spend any more time on it. |
51 |
> |
52 |
> Many thanks for your help, Tom |
53 |
|
54 |
You're welcome, with apologies for the delayed response. |