Thanks! Please keep me updated if you find put more or when a updated version
is available.
As I now know it is working, I will start tomorrow to build up a testsystem
with 3 NFS servers (two of them in a ha with CARP and HAST) and several ESXi
hosts which will all access there NFS datastores
On Sat, 2018-03-10 at 23:42 +, Pete French wrote:
> >
> > It looks like r330745 applies fine to stable-11 without any changes,
> > and there's plenty of value in testing that as well, if you're already
> > set up for that world.
> >
>
> Ive been running the patch from the PR in production
It looks like r330745 applies fine to stable-11 without any changes,
and there's plenty of value in testing that as well, if you're already
set up for that world.
Ive been running the patch from the PR in production since the original
bug report and it works fine. I havent looked at
On Sat, 2018-03-10 at 23:08 +, Pete French wrote:
> Ah, thankyou! I haven;t run current before, but as this is such an issue
> for us I;ll setup an Azure machine running it and have it reboot every
> five minutes or so to check it works OK. Unfortunately the error doesnt
> show up
Ah, thankyou! I haven;t run current before, but as this is such an issue
for us I;ll setup an Azure machine running it and have it reboot every
five minutes or so to check it works OK. Unfortunately the error doesnt
show up consisntently, as its a race condition. Will let you know if it
fails
On Sat, 2018-03-03 at 16:19 +, Pete French wrote:
>
> >
> > That won't work for the boot drive.
> >
> > When no boot drive is detected early enough, the kernel goes to the
> > mountroot prompt. That seems to hold a Giant lock which inhibits
> > further progress being made. Sometimes
NAGY Andreas wrote:
>Thanks, the not issuing delegation warnings disappeared with this patch.
>
>But now there are some new warnings I haven't seen so far:
>2018-03-10T13:01:39.441Z cpu8:68046)WARNING: NFS41: NFS41FSOpGetObject:2148:
>Failed to >get object 0x43910e71b386 [36 c6b10167 9b157f95
Thanks, the not issuing delegation warnings disappeared with this patch.
But now there are some new warnings I haven't seen so far:
2018-03-10T13:01:39.441Z cpu8:68046)WARNING: NFS41: NFS41FSOpGetObject:2148:
Failed to get object 0x43910e71b386 [36 c6b10167 9b157f95 5aa100fb 8ffcf2c1 c 2