[Bug 300380] NFSv4.2 server: NFSv4.1 FATTR4_SPACE_USED attribute after NFSv4.2 COPY+COMMIT returns value before COPY+COMMIT

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 31 Oct 2026 14:30:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300380

--- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> ---
Were they using ZFS storage?
If so, the COPY was probably done via block
cloning, which means the storage use wouldn't
change until one of the copies is written, I
would think? (I'm not a ZFS guy.)

ZFS also uses compression by default, so
the space used is typically less than some
would expect.

All the server does is report whatever the
server's exported fs reports. Whoever reported
this to you should try a test locally on the
server and see what happens then.

I am not sure what you mean by a "normal GETATTR".
One done in the same compound as the COPY+COMMIT
is handled the same way as one done in another
compound.

-- 
You are receiving this mail because:
You are the assignee for the bug.