Am 2023-11-18 04:30, schrieb Rick Macklem:
On Fri, Nov 17, 2023 at 7:10 PM Garrett Wollman
wrote:
<
said:
> Looks like main still has this problem. I exported a ZFS file system from
> a 15-current system to the same 13.2 client, and it exhibits the problem
> (EIO from NFSv3). So the
On Fri, Nov 17, 2023 at 7:10 PM Garrett Wollman wrote:
>
> < said:
>
> > Looks like main still has this problem. I exported a ZFS file system from
> > a 15-current system to the same 13.2 client, and it exhibits the problem
> > (EIO from NFSv3). So the problem is most likely in 14.0 as well.
>
< said:
> Looks like main still has this problem. I exported a ZFS file system from
> a 15-current system to the same 13.2 client, and it exhibits the problem
> (EIO from NFSv3). So the problem is most likely in 14.0 as well.
Glad someone was able to reproduce. I don't have any systems I can
On 17 Nov 2023, at 17:22, Mike Karels wrote:
> On 17 Nov 2023, at 16:35, Garrett Wollman wrote:
>
>> < said:
>>
>>> I have not run into this, so I tried it just now. I had no problem.
>>> The server is 13.2, fully patched, the client is up-to-date -current,
>>> and the mount is v4.
>>
>> On my
On 17 Nov 2023, at 16:35, Garrett Wollman wrote:
> < said:
>
>> I have not run into this, so I tried it just now. I had no problem.
>> The server is 13.2, fully patched, the client is up-to-date -current,
>> and the mount is v4.
>
> On my 13.2 client and 13-stable server, I see:
I set up ZFS on
< Looking at this from the RPC side:
> (PUTFH, GETATTR, LOOKUP(snapshotname), GETFH, GETATTR)
> [NFS4_OK for all ops]
> (PUTFH, GETATTR)
> [NFS4_OK, NFS4_OK]
> (PUTFH, ACCESS(0x3f), GETATTR)
> [NFS4_OK, NFS4_OK, rights = 0x03, NFS4_OK]
>
< said:
> I have not run into this, so I tried it just now. I had no problem.
> The server is 13.2, fully patched, the client is up-to-date -current,
> and the mount is v4.
On my 13.2 client and 13-stable server, I see:
25034 ls CALL
open(0x237d32f9a000,0x120004)
25034 ls NAMI
On 17 Nov 2023, at 15:04, Garrett Wollman wrote:
> Hi, all,
>
> One other regression that we found after upgrading from 12.4 to 13.2
> on our NFS servers is that ZFS snapshots of exported filesystems are
> no longer accessible to NFS clients. The .zfs/snapshot directory is
> readable, and can
Hi, all,
One other regression that we found after upgrading from 12.4 to 13.2
on our NFS servers is that ZFS snapshots of exported filesystems are
no longer accessible to NFS clients. The .zfs/snapshot directory is
readable, and can stat(2) the individual snapshot directories, but
attempting to
