mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2021-08-30 12:02:52 -04:00
parent e2038ef412
commit 50bb5f9c47
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/comment_14_66d72d1d214124eaa57681df21b9b121._comment Normal file
View file

@ -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..
"""]]