https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030
--- Comment #22 from Rick Macklem <[email protected]> --- (In reply to Martin Birgmeier from comment #0) This problem might be caused by an older NFSv4 server, although I have no idea why the file has uarch set. Let me explain... Commit 3b6d4c6 added support for the NFSv4 Archive attribute (uarch) to the NFSv4 client/server. This implies that the NFSv4 client now checks to see if the NFSv4 server supports the Archive attribute. However, if the NFSv4 server is an older one (prior to the above commit done to main on Oct. 21), the server will say that Archive is not supported. Is your NFS mount using NFSv4 and is your NFSv4 server a FreeBSD one that isn't completely up to date? If so, I think I have to come up with a better way to handle an NFSv4 server that does not support Archive (uarch). (I'm away from home for a couple of weeks, so I won't be able to come up with any patch for a while.) -- You are receiving this mail because: You are the assignee for the bug.
