[Bug 296088] nfscl: chflags(<file>, 0) on an NFSv4.x mount returns EIO instead of being handled as a NOP.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296088

Rick Macklem <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
                 CC|                            |[email protected]

--- Comment #2 from Rick Macklem <[email protected]> ---
Well, it was actually commits c5d72d2 and 3b6d4c6, which only checked
for support if the archive/hidden/system attributes were non-zero.
Specifying chflags(<path>, 0) set them to zero, so it
didn't fail this check, but attempted to set them to false on
the server when the server did not support one or more of these
attributes.

The patch in the attachment should fix this.

Btw, "chflags(<path>, 0)" is not a no-op, for ZFS stores
(and NFS servers exporting them) it clears the UF_ARCHIVE
(uarch) bit, which is set for any new file created on ZFS.

You didn't mention what NFS server you were using, but
I'll assume it was one that does not support all of the
archive/hidden/system attributes.

Please test the patch in the attachment and let us know
if it fixed the problem for you?

Thanks for reporting this, rick

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