Date: Sun, 10 Oct 2021 01:11:47 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd Message-ID: <YQXPR0101MB0968322C2DEBFAA672FFBC8EDDB49@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | raw e-mail | index | archive | help
Hi,=0A= =0A= I ran into an issue this week during the nfsv4@ietf.org's testing event.=0A= UFS - supports VOP_ALLOCATE() by using vop_stdallocate().=0A= ZFS - just return EINVAL for VOP_ALLOCATE().=0A= =0A= An NFSv4.2 server can either support Allocate or not, but it has to be=0A= for all exported file systems.=0A= =0A= This leads me to a couple of questions:=0A= - Is there a good reason for not using vop_stdallocate() for ZFS?=0A= - Should I try and support both file system types via vop_stdallocate()=0A= or not support Allocate at all?=0A= =0A= Btw, as a bit of an aside, "cc" uses posix_fallocate() and in weird ways,= =0A= such as offset=3D0, len=3D1. Why, I have no idea?=0A= =0A= Thanks in advance for any comments, rick=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968322C2DEBFAA672FFBC8EDDB49>