Skip site navigation (1)Skip section navigation (2) 
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>
index | next in thread | raw e-mail 

Hi,

I ran into an issue this week during the nfsv4@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 to a couple of questions:
- Is there a good reason for not using vop_stdallocate() for ZFS?
- Should I try and support both file system types via vop_stdallocate()
  or not support Allocate at all?

Btw, as a bit of an aside, "cc" uses posix_fallocate() and in weird ways,
such as offset=0, len=1. Why, I have no idea?

Thanks in advance for any comments, rick
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968322C2DEBFAA672FFBC8EDDB49>