On Tue, Feb 3, 2015 at 7:05 PM, walt wrote:
> On 02/03/2015 03:29 AM, Tom H wrote:
>> On Mon, Feb 2, 2015 at 8:46 PM, walt wrote:
>>>
>>> This morning I got "waiting on lockfile foo in /usr/portage/distfiles"
>>> "locking not available" from my nfs3 clients when trying to download
>>> needed sour
On 02/03/2015 03:29 AM, Tom H wrote:
> On Mon, Feb 2, 2015 at 8:46 PM, walt wrote:
>> 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 don't recall having this problem back
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
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 does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 02.02.2015 um 22:35 schrieb Neil Bothwick:
> On Mon, 02 Feb 2015 19:02:24 +0100, Stefan G. Weichinger wrote:
>
>> I applied the patch from Comment 9 to nfs-utils-1.3.2-r1 but
>> rpc-statd.service doesn't start either.
>>
>> Do I have to downgrade
On Mon, 02 Feb 2015 19:02:24 +0100, Stefan G. Weichinger wrote:
> I applied the patch from Comment 9 to nfs-utils-1.3.2-r1 but
> rpc-statd.service doesn't start either.
>
> Do I have to downgrade as well?
> I don't fully understand that from the comments there.
You need to set CONFIG_NFS_V4_2.
On Sun, Feb 1, 2015 at 9:15 PM, Rich Freeman wrote:
>
> I believe that starting nfs-client.service or nfs-server.service
> starts everything needed EXCEPT rpcbind. I'd have to re-trace
> everything, but I think that there are multiple packages involved here
> and the upstream units don't include
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
On 02.02.2015 16:55, Holger Hoffstätte wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=538372
>
> Explanations & fixes.I have it running on both server & client (with
> openrc). Refusing to set NFS_V4_2 on the client may break things since
> it's apparently the default for protocol negotiation
On Mon, Feb 2, 2015 at 10:55 AM, Holger Hoffstätte
wrote:
> On Mon, 02 Feb 2015 16:33:53 +0100, Stefan G. Weichinger wrote:
>
>> didn't read the whole thread, sorry ... but I also noticed my
>> nfsv4-server stopped working with that latest update.
>>
>> Some systemd-service-files were renamed and/
On Mon, 02 Feb 2015 16:33:53 +0100, Stefan G. Weichinger wrote:
> didn't read the whole thread, sorry ... but I also noticed my
> nfsv4-server stopped working with that latest update.
>
> Some systemd-service-files were renamed and/or removed, right?
No, it's (ironically) a systemd-specific bug.
On Mon, Feb 2, 2015 at 10:19 AM, wrote:
>
> Thanks for the explanation. My NFS servers are running Ubuntu 14.04.1
> LTS. Only my clients are gentoo systems. And on the clients I have no
> NFS 4 support in the kernel and I also don't have to specify nfsver=4.
> Maybe this problem only occurs with
On 02.02.2015 16:19, waben...@gmail.com wrote:
> Thanks for the explanation. My NFS servers are running Ubuntu 14.04.1
> LTS. Only my clients are gentoo systems. And on the clients I have no
> NFS 4 support in the kernel and I also don't have to specify nfsver=4.
> Maybe this problem only occurs
Am Montag, 02.02.2015 um 08:37
schrieb Neil Bothwick :
> On Mon, 2 Feb 2015 02:01:11 +0100, waben...@gmail.com wrote:
>
> > > It's got nothing to do with the init system used. That message
> > > tells you what to do to try to mount the NFS shares when you
> > > boot, but unless you have suitable
On Mon, 2 Feb 2015 02:01:11 +0100, waben...@gmail.com wrote:
> > It's got nothing to do with the init system used. That message tells
> > you what to do to try to mount the NFS shares when you boot, but
> > unless you have suitable mount options or kernel config, that attempt
> > will fail.
>
>
On Sun, Feb 1, 2015 at 8:35 PM, wrote:
> Am Sonntag, 01.02.2015 um 16:31
> schrieb walt :
>
>> For example, I had to add the rpcbind.service to the multi-user
>> systemd target because even nfs3 seems to need it. (I knew when I
>
> I never used systemd, so I don't know if adding the rpcbind.servi
Am Sonntag, 01.02.2015 um 16:31
schrieb walt :
> For example, I had to add the rpcbind.service to the multi-user
> systemd target because even nfs3 seems to need it. (I knew when I
I never used systemd, so I don't know if adding the rpcbind.service to
the multi-user systemd target is also startin
Am Sonntag, 01.02.2015 um 16:31
schrieb walt :
> Thanks wabe. I forgot to mention that I use systemd now, and I've
> had to work out a few problems with nfs over past months because our
> gentoo systemd scripts are lagging a bit behind upstream, which is
> not surprising.
>
> For example, I had
Am Montag, 02.02.2015 um 00:12
schrieb Neil Bothwick :
> On Mon, 2 Feb 2015 00:32:34 +0100, waben...@gmail.com wrote:
>
> > > #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs
> > > indefinitely until I hit Ctrl-C. If I then repeat the same
> > > command immediately the mount succeeds
On 02/01/2015 03:32 PM, waben...@gmail.com wrote:
> Am Sonntag, 01.02.2015 um 14:41
> schrieb walt :
>
>> On 02/01/2015 01:18 PM, walt wrote:
>>> I was happy with nfs3 until it stopped working for reasons I still
>>> don't understand :(
>>
>> Well, nfs3 still works, but only after failing on the f
On Mon, 2 Feb 2015 00:32:34 +0100, waben...@gmail.com wrote:
> > #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs
> > indefinitely until I hit Ctrl-C. If I then repeat the same command
> > immediately the mount succeeds. This is the mysterious nfs black
> > magic I've run into many t
Am Sonntag, 01.02.2015 um 14:41
schrieb walt :
> On 02/01/2015 01:18 PM, walt wrote:
> > I was happy with nfs3 until it stopped working for reasons I still
> > don't understand :(
>
> Well, nfs3 still works, but only after failing on the first attempt:
>
> #mount.nfs a6://usr/portage /usr/portag
On 02/01/2015 01:18 PM, walt wrote:
> I was happy with nfs3 until it stopped working for reasons I still don't
> understand :(
Well, nfs3 still works, but only after failing on the first attempt:
#mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs indefinitely
until I hit Ctrl-C. If I t
23 matches
Mail list logo
