On Tue, Jun 19, 2018 at 5:11 AM, Rick Macklem wrote:
> Steve Wills wrote:
> On 06/18/18 17:42, Rick Macklem wrote:
> >> Steve Wills wrote:
> >>> Would it be possible or reasonable to use the client ID to log a
> message
> >>> telling the admin to enable a sysctl to enable the hacks?
> >> Yes.
Steve Wills wrote:
On 06/18/18 17:42, Rick Macklem wrote:
>> Steve Wills wrote:
>>> Would it be possible or reasonable to use the client ID to log a message
>>> telling the admin to enable a sysctl to enable the hacks?
>> Yes. However, this client implementation id is only seen by the server
>>
Hi,
On 06/18/18 17:42, Rick Macklem wrote:
Steve Wills wrote:
Would it be possible or reasonable to use the client ID to log a message
telling the admin to enable a sysctl to enable the hacks?
Yes. However, this client implementation id is only seen by the server
when the client makes a mount
essage and fail the mount, if the "hack" sysctl
isn't
set?
rick
[stuff snipped]
From: Steve Wills
Sent: Monday, June 18, 2018 5:21:10 PM
To: Rick Macklem; freebsd-current@freebsd.org
Cc: andreas.n...@frequentis.com
Subject: Re: ESXi NFSv4.1 cl
My thoughts on this are mixed.
You need certain workarounds, but they sound like they need to be on a
per-client-type basis.
On the one hand, you don't want to chat with different clients differently,
but on the other you want it to work.
I'd suggest a two-tiered approach.
First, have a sysctl
Would it be possible or reasonable to use the client ID to log a message
telling the admin to enable a sysctl to enable the hacks?
Steve
On 06/17/18 08:35, Rick Macklem wrote:
Hi,
Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi 6.5u1
(VMware) against the FreeBSD
On Sun, Jun 17, 2018 at 12:35:12PM +, Rick Macklem wrote:
> Hi,
>
> Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi
> 6.5u1
> (VMware) against the FreeBSD server. I have given him a bunch of hackish
> patches
> to try and some of them do help. However not all
Hi,
Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi 6.5u1
(VMware) against the FreeBSD server. I have given him a bunch of hackish patches
to try and some of them do help. However not all issues are resolved.
The problem is that these hacks pretty obviously violate the
