From: Joey Hess Date: Mon, 30 Aug 2021 16:02:52 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~87^2~39 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=50bb5f9c4778ac1193743760f1f969e30e6c61fa;p=git-annex.git comment --- diff --git a/doc/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/comment_14_66d72d1d214124eaa57681df21b9b121._comment b/doc/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/comment_14_66d72d1d214124eaa57681df21b9b121._comment new file mode 100644 index 0000000000..4113a8574d --- /dev/null +++ b/doc/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/comment_14_66d72d1d214124eaa57681df21b9b121._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 14""" + date="2021-08-30T15:59:29Z" + content=""" +It seems likely to me that this NFS server is just broken. Why would a +well-designed NFS server behave this way, rather than letting a chmod +override the xattr that was set earlier? + +I considered filing a bug report on coreutils or something about cp +preserving the NFS xattr leading to this problem, but since it seems likely +to be the NFS server on the NAS that is at fault, didn't think that would +be productive. + +If you did manage to reproduce that behavior with a regular +linux NFS server, it seems like it would be a grounds for a bug on some +part of linux.. +"""]]