Extended attribute
An extended attribute is a named metadata value associated with a filesystem object in addition to its ordinary file attributes.
Linux scope: names include a namespace, such as user, security, system or trusted, with different access policies. A defined empty value is not an absent attribute. Access to a value and visibility of its name are separate concerns: listxattr() may omit names inaccessible to the caller. An unprivileged user.* inventory therefore does not establish equality of all metadata. [1] [2]
Restore acceptance: matching all source name/value pairs does not exclude destination-only names. In 132 controlled executions on one host, GNU tar 1.35 preserved an extra attribute on an existing directory while restoring both source values; the regular file was recreated. Unfiltered rsync 3.2.7 -aX reconciled the visible user.* sets, while an explicit exclusion retained the extra key. These outcomes concern the recorded options and fixtures, not all namespaces or future versions. [4]
Isolation: metadata-only rsync updates in the same study also changed a retained hard-link alias outside the destination subtree. A changed-payload control replaced the destination file and left its old alias intact; neither used --inplace. Path containment alone is not metadata isolation. These are repeatability controls on ext4 and tmpfs, not independent systems or crash-durability measurements. [4]
ACL options: rsync -aX does not imply -A. Filesystem support, authority and application meaning still need validation. [3]
Relations
- related
- Hard link, POSIX access control list
Advantages
- Stores named metadata alongside a filesystem object.
Limitations
- Namespace support, permissions and backup-tool policies vary.
- Matching visible attributes alone does not prove complete recovery or application access.
Citations
- Linux man-pages: xattr(7), namespaces and empty values
- Linux man-pages: listxattr(2), caller-visible names
- Official rsync manual: attribute filters and ACL options
- Hesela: native xattr restore protocol and reproducible evidence
Sources & caveats
- Controlled user.* fixtures: 11 scenarios, two filesystem types, three repetitions and two captures on one Linux host. No privileged metadata, cross-host restore, crash or independent replication.