Message 246278 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	minrk
Recipients	jhamrick, minrk
Date	2015年07月04日.21:19:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1436044763.77.0.446789512383.issue24564@psf.upfronthosting.co.za>

Content
On a bit of further investigation, the NFS files have an xattr `system.nfs4_acl`. This can be read, but attempting to write it fails with EINVAL. Attempting to copy from NFS to non-NFS fails with ENOTSUP, which is caught and ignored, but copying from NFS to NFS raises EINVAL, which raises. Adding `EINVAL` to the ignored errnos would fix the problem, but might hide real failures (I'm not sure about the real failures, but it seems logical). Since the `copy_function` is customizable to switch between `copy` and `copy2`, making copystat optional on files, perhaps the `copystat` should be optional on directories, as well.

Content

On a bit of further investigation, the NFS files have an xattr `system.nfs4_acl`. This can be read, but attempting to write it fails with EINVAL. Attempting to copy from NFS to non-NFS fails with ENOTSUP, which is caught and ignored, but copying from NFS to NFS raises EINVAL, which raises.
Adding `EINVAL` to the ignored errnos would fix the problem, but might hide real failures (I'm not sure about the real failures, but it seems logical).
Since the `copy_function` is customizable to switch between `copy` and `copy2`, making copystat optional on files, perhaps the `copystat` should be optional on directories, as well.

History
Date	User	Action	Args
2015年07月04日 21:19:23	minrk	set	recipients: + minrk, jhamrick
2015年07月04日 21:19:23	minrk	set	messageid: <1436044763.77.0.446789512383.issue24564@psf.upfronthosting.co.za>
2015年07月04日 21:19:23	minrk	link	issue24564 messages
2015年07月04日 21:19:23	minrk	create

homepage