AzCopy fails to write xattr #2761
Assignees
Comments
|
Command log: Scanning log: |
|
Installed xattr: |
|
https://go.googlesource.com/sys.git/+/master/unix/xattr_bsd.go#31 func xattrnamespace(fullattr string) (ns int, attr string, err error) {
s := strings.IndexByte(fullattr, '.')
if s == -1 {
return -1, "", ENOATTR
}
namespace := fullattr[0:s]
attr = fullattr[s+1:]
switch namespace {
case "user":
return EXTATTR_NAMESPACE_USER, attr, nil
case "system":
return EXTATTR_NAMESPACE_SYSTEM, attr, nil
default:
return -1, "", ENOATTR
}
} |
|
Fix suggested: #2762 |
|
Hi there. Apologies for the delayed response. Xattr has to be available at a filesystem level, which is usually a flag when mounting the fs. There are two potential mitigations here
|
OS agnostic solution also has its own issue as I described in issue description. |
|
|
|
@adreed-msft I tested my changes from PR #2762 and it works as expected. |
|
More information about ENOTSUP: https://manpages.debian.org/unstable/manpages-dev/setxattr.2.en.html#EDQUOT |
|
Got the same.... 2024/11/27 10:20:48 failed to write hash data for ._data01: failed to write xattr: operation not supported; consider utilizing an OS-agnostic hash storage mode Use the XFS filesystem: /dev/sdb1 on /data type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.25.1
Which platform are you using? (ex: Windows, Mac, Linux)
Linux (Ubuntu 22.04 VM in Azure)
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy sync "https://<storageName>.blob.core.windows.net/<container>/<folder>/?<sig>" "." --delete-destination true --compare-hash "MD5" --cap-mbps 400
What problem was encountered?
When trying to sync files from storage account to Ubuntu 22.04 I getting xattr related errors:
Important! Even when it shows errors in the log and shows all operations as failed, it downloads files anyway.
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
I installed xattr package, but it didn't help.
Tried to use OS agnostic way, but there is another issue with it #2758
The potential reason for this issue is that you are trying to write xattr without "user." prefix. I tried to set xattrs for test file by command
xattr -w sss testVal test.xmland it failed with error[Errno 95] Operation not supported: b'test.xml', but it works asxattr -w user.sss testVal test.xml.As far as I understand, user_xattr is enabled for ext4 filesystem by default. Also, I tried to enable it explicitly (via /etc/fstab).
It is described here: https://stackoverflow.com/questions/60893372/why-must-a-user-be-prepended-to-the-name-when-setting-a-files-xattr-with-os
The text was updated successfully, but these errors were encountered: