Date: Mon, 17 Oct 2022 00:19:14 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: RFC: ZFS does not update ctime/va_filerev upon Setextattr/rmextattr Message-ID: <YQXPR01MB41508ACC6E2D6E7478648A10DD299@YQXPR01MB4150.CANPRD01.PROD.OUTLOOK.COM>
next in thread | raw e-mail | index | archive | help
Hi,=0A=
=0A=
At a recent IETF NFSv4 testing event, it was noted that=0A=
neither ctime nor va_filerev (called TimeMetadata in NFSv4)=0A=
were being updated when a Setextattr or Removeextattr=0A=
was being done on a file on ZFS. (Looking at the ZFS code,=0A=
this is pretty obviously the case, since ZFS really uses subfiles=0A=
and not extended attributes on the file.)=0A=
=0A=
A Linux wizard says that ctime should be updated, although=0A=
there is no POSIX standard. I suspect that FreeBSD's extended=0A=
attributes are meant to mimic the Linux ones?=0A=
=0A=
So, is this a bug that should be fixed in ZFS or something where=0A=
the NFS server does a workaround to make the Setxattr/Rmxattr=0A=
NFSv4.2 operations work per the RFC?=0A=
=0A=
rick=0A=
ps: It looks like a zfs_tstamp_update_setup() needs to be added=0A=
to the ZFS setextattr/removeextattr VOP calls for a ZFS fix,=0A=
but I have no idea what the rest of the patch would need to=0A=
look like?=0A=
=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR01MB41508ACC6E2D6E7478648A10DD299>