Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-13 Thread Stefan Esser
Am 10.10.21 um 05:52 schrieb Alan Somers: > On Sat, Oct 9, 2021 at 7:13 PM Rick Macklem wrote>> > This leads me to a couple of questions: >> - Is there a good reason for not using vop_stdallocate() for ZFS? > > Yes. posix_fallocate is supposed to guarantee that subsequent writes > to the file

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Willem Jan Withagen via freebsd-current
On 10-10-2021 07:57, Rick Macklem wrote: This leads me to a couple of questions: - Is there a good reason for not using vop_stdallocate() for ZFS? Yes. posix_fallocate is supposed to guarantee that subsequent writes to the file will not fail with ENOSPC. But ZFS, being a copy-on-write file

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Rick Macklem
later to rewrite those same offsets, ZFS > will actually allocate new LBAs for them. Eighto. I get it now. Looks like I must disable it in the server, unless there is a way to enable it on a per file system basis (which I don not believe is the case for NFSv4.2, although that isn't complete

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Alan Somers
t; UFS - supports VOP_ALLOCATE() by using vop_stdallocate(). > >> ZFS - just return EINVAL for VOP_ALLOCATE(). > >> > >> An NFSv4.2 server can either support Allocate or not, but it has to be > >> for all exported file systems. > > > >That seems like a pr

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Warner Losh
ports VOP_ALLOCATE() by using vop_stdallocate(). > >> ZFS - just return EINVAL for VOP_ALLOCATE(). > >> > >> An NFSv4.2 server can either support Allocate or not, but it has to be > >> for all exported file systems. > > > >That seems like a protocol bu

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-09 Thread Rick Macklem
Alan Somers wrote: >On Sat, Oct 9, 2021 at 7:13 PM Rick Macklem wrote: >> >> Hi, >> >> I ran into an issue this week during the nf...@ietf.org's testing event. >> UFS - supports VOP_ALLOCATE() by using vop_stdallocate(). >> ZFS - just return EINVAL for VOP_

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-09 Thread Rick Macklem
From: Alan Somers Sent: Saturday, October 9, 2021 11:52 PM To: Rick Macklem Cc: FreeBSD Current Subject: Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd CAUTION: This email originated from outside of the University of Guelph. Do not click links or open

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-09 Thread Alan Somers
On Sat, Oct 9, 2021 at 7:13 PM Rick Macklem wrote: > > Hi, > > I ran into an issue this week during the nf...@ietf.org's testing event. > UFS - supports VOP_ALLOCATE() by using vop_stdallocate(). > ZFS - just return EINVAL for VOP_ALLOCATE(). > > An NFSv4.2 server can

RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-09 Thread Rick Macklem
Hi, I ran into an issue this week during the nf...@ietf.org's testing event. UFS - supports VOP_ALLOCATE() by using vop_stdallocate(). ZFS - just return EINVAL for VOP_ALLOCATE(). An NFSv4.2 server can either support Allocate or not, but it has to be for all exported file systems. This leads me

Re: Heads up: Large patch that adds NFSv4.2 has been committed to head/current

2019-12-13 Thread Evilham
On dv., des. 13 2019, Rick Macklem wrote: Hi, r355677 is a large patch that adds NFSv4.2 support to the NFS client/server. It has survived a "make universe" for all arches that would build (some mips and sparc64 failed for reasons unrelated to this patch). However, I have not

Heads up: Large patch that adds NFSv4.2 has been committed to head/current

2019-12-12 Thread Rick Macklem
Hi, r355677 is a large patch that adds NFSv4.2 support to the NFS client/server. It has survived a "make universe" for all arches that would build (some mips and sparc64 failed for reasons unrelated to this patch). However, I have not been able to do a build with a recent GCC. If there

merge of NFSv4.2 support into head/current

2019-11-25 Thread Rick Macklem
Hi, I have completed development and a testing cycle for the NFSv4.2 (RFC-7862) code in base/projects/nfsv42 on subversion. NFSv4.2 is a minor revision to NFSv4.1 and adds support for the following optional features: - lseek(SEEK_DATA/SEEK_HOLE) - posix_fallocate() - posix_fadvise

Re: NFSv4.2

2017-12-11 Thread Rick Macklem
Stefan Wendler wrote: > We would like to use the file copy and the sparse features of 4.2 in our > Setup. Do you know if any of the two has been implemented yet? The > sparse feature would be more important than the file copy feature though. No idea (except that NFSv4.2 isn't in Free

Re: NFSv4.2

2017-12-11 Thread Stefan Wendler
On 12/11/2017 13:15, Rick Macklem wrote: > Stefan Wendler wrote: >> I was wondering when and if FreeBSD will support NFSv4.2 >> Is there anything planned yet? > Someday, but no specific plans at this point. > > Is there some specific feature in NFSv4.2 that you are look

Re: NFSv4.2

2017-12-11 Thread Rick Macklem
Stefan Wendler wrote: > I was wondering when and if FreeBSD will support NFSv4.2 > Is there anything planned yet? Someday, but no specific plans at this point. Is there some specific feature in NFSv4.2 that you are looking for? I ask because there isn't a lot of new features in N

NFSv4.2

2017-12-11 Thread Stefan Wendler
Hi, I was wondering when and if FreeBSD will support NFSv4.2 Is there anything planned yet? Thx and Cheers, Stefan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail