| 1 |
On 02/02/2015 10:29 AM, Tom H wrote: |
| 2 |
> On Sun, Feb 1, 2015 at 7:31 PM, walt <w41ter@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> For example, I had to add the rpcbind.service to the multi-user |
| 5 |
>> systemd target because even nfs3 seems to need it. |
| 6 |
> |
| 7 |
> You must mean "because especially nfsv3 needs it" because, |
| 8 |
> theoretically, nfsv4 doesn't need rpcbind since an nfsv4 mount only |
| 9 |
> needs to now about rpc.nfsd's default port 2049. |
| 10 |
|
| 11 |
Tom, you obviously know nfs better than I do, so maybe you can answer |
| 12 |
this question for me. |
| 13 |
|
| 14 |
This morning I got "waiting on lockfile foo in /usr/portage/distfiles" |
| 15 |
"locking not available" from my nfs3 clients when trying to download |
| 16 |
needed source files. |
| 17 |
|
| 18 |
I worked around this failure by using the nfs nolock mount option, and |
| 19 |
then I gave up and restored nfs4 to all my kernels and nfs-utils packages. |
| 20 |
|
| 21 |
I don't recall having this problem back in my former nfs3-only days. |
| 22 |
Maybe I've forgotten something obvious that I did back then? |
Archives