[Bug 293691] NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets EPERM for file/dir creation attempts
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 293691] NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets EPERM for file/dir creation attempts"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 293691] NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets EPERM for file/dir creation attempts"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 09 Mar 2026 16:38:15 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293691
Bug ID: 293691
Summary: NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets
EPERM for file/dir creation attempts
Product: Base System
Version: 16.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: roland.mainz@nrubsig.org
FreeBSD installed from
FreeBSD-16.0-CURRENT-amd64-20260302-5d9b185c33ae-284268-disc1.iso
NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets EPERM for file/dir creation
attempts.
This looks like a variation of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292283 ("Bug 292283 - (JAVA)
NFSv4.1 client trying to set FATTR4_SYSTEM or FATTR4_HIDDEN gets EPERM for file
and dir creation attemps"), since the same workaround in the Windows
ms-nfs41-client NFSv4.1 client works if extended to |FATTR4_ARCHIVE| - see
https://github.com/kofemann/ms-nfs41-client/commit/7156d9f9deb25843e57fd455d8ec67951b82c737
--
You are receiving this mail because:
You are the assignee for the bug.