Hi,
I am trying to get a FreeBSD NFS 4.1 export working with VMware Esxi 6.5u1, but
it is always mounted as read only.
After some research, I found out that this is a known problem, and there are
threads about this from 2015 also in the mailinglist archive.
As it seems VMware will not change t
v.c 4102
lines.
andi
-Original Message-
From: Rick Macklem [mailto:rmack...@uoguelph.ca]
Sent: Samstag, 3. März 2018 03:01
To: NAGY Andreas ; freebsd-stable@freebsd.org
Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi
client
NAGY Andreas wrote:
>I am
-Original Message-
From: Rick Macklem [mailto:rmack...@uoguelph.ca]
Sent: Sonntag, 4. März 2018 06:48
To: NAGY Andreas ; freebsd-stable@freebsd.org
Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi
client
NAGY Andreas wrote:
>Hi and thanks!
>
>First t
quiet well, but I now want to switch to NFS, and hope to get
equivalent speeds.
Thanks so far,
andi
-Original Message-
From: NAGY Andreas
Sent: Sonntag, 4. März 2018 14:26
To: Rick Macklem ; freebsd-stable@freebsd.org
Subject: RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in
: Montag, 5. März 2018 02:16
To: NAGY Andreas ; 'freebsd-stable@freebsd.org'
Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi
client
NAGY Andreas wrote:
[stuff snipped]
>In the source I saw nfs_async = 0; is it right that NFS will work in async
>mode i
Compiling with the last patch also failed:
error: use of undeclared identifier 'NFSV4OPEN_WDSUPPFTYPE'
-Original Message-----
From: NAGY Andreas
Sent: Montag, 5. März 2018 14:22
To: Rick Macklem ; 'freebsd-stable@freebsd.org'
Subject: RE: NFS 4.1 RECLAIM_COMPLET
Okay, that was the main reason for using NFS 4.1.
Is it planned to implement it, or is the focus on pNFS?
Thanks,
Andi
Von: Rick Macklem
Gesendet: 05.03.2018 11:49 nachm.
An: NAGY Andreas; 'freebsd-stable@freebsd.org'
Betreff: Re: NFS 4.1 RECLAIM_C
acklem [mailto:rmack...@uoguelph.ca]
Sent: Mittwoch, 7. März 2018 16:07
To: NAGY Andreas ; 'freebsd-stable@freebsd.org'
Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi
client
NAGY Andreas wrote:
>Okay, that was the main reason for using NFS 4.1.
>Is i
de a trace on one of the two links.
(nfs41_trace_before_reboot.pcap and nfs41_trace_after_reboot.pcap)
https://files.fm/u/wvybmdmc
andi
-Original Message-
From: Rick Macklem [mailto:rmack...@uoguelph.ca]
Sent: Donnerstag, 8. März 2018 03:48
To: NAGY Andreas ; 'freebsd-stable@freebs
>The attached patch changes BindConnectiontoSession to reply
>NFS4ERR_BAD_SESSION when the session doesn't exist. This might trigger
>recovery after a server reboot.
>This patch must be applied after bindconn.patch.
Works perfect! ESXi host reconnects to the datastore as soon as the nfsserver
i
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
9f22ad6
over 4 uplinks with NICs on
different subnets.
It should always be possible to do there some testing.
andi
Von: Rick Macklem
Gesendet: 10.03.2018 11:20 nachm.
An: NAGY Andreas; 'freebsd-stable@freebsd.org'
Betreff: Re: NFS 4.1 RECLAIM_COMPLETE FS faile
Hi! Sorry, I did not forget the traces, but had no time so far and as I am
actually setting up several servers on the system I don't want to break
anything by performing tests. I will send them as soon I have finished my
actual work. Will be at least end of this week.
As I am actually setting u
13 matches
Mail list logo
