Extended file attributes

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Extended file attributes is a file system feature that enables users to associate computer files with metadata not interpreted by the filesystem, whereas regular attributes have a purpose strictly defined by the filesystem (such as permissions or records of creation and modification times). Unlike forks, which can usually be as large as the maximum file size, extended attributes are usually limited in size to a value significantly smaller than the maximum file size. Typical uses include storing the author of a document, the character encoding of a plain-text document, or a checksum, cryptographic hash or digital signature.

Implementations[edit]

AIX[edit]

In AIX, the JFS2 v2 filesystem supports extended attributes, which are accessible using the getea command.[1] The getea,[2] setea,[3] listea,[4] statea,[5] and removeea[6] APIs support fetching, setting, listing, getting information about, and removing extended attributes.

FreeBSD[edit]

In FreeBSD 5.0 and later, the UFS1 and UFS2 filesystems support extended attributes, using the extattr_[7] family of system calls. Any regular file may have a list of extended attributes. Each attribute consists of a name and the associated data. The name must be a null-terminated string, and exists in a namespace identified by a small-integer namespace identifier. Currently, two namespaces exist: user and system. The user namespace has no restrictions with regard to naming or contents. The system namespace is primarily used by the kernel for access control lists and mandatory access control. Since FreeBSD 8.0, extended attributes are also supported on ZFS filesystem.[citation needed]

Linux[edit]

In Linux, the ext2, ext3, ext4, JFS, Squashfs, ReiserFS, XFS, Btrfs, Lustre, and OCFS2 1.6 filesystems support extended attributes (abbreviated xattr) when enabled in the kernel configuration. Any regular file or directory may have extended attributes consisting of a name and associated data. The name must be a null-terminated string prefixed by a namespace identifier and a dot character. Currently, four namespaces exist: user, trusted, security and system. The user namespace has no restrictions with regard to naming or contents. The system namespace is primarily used by the kernel for access control lists. The security namespace is used by SELinux, for example.

Extended attributes are not widely used in user-space programs in Linux, although they are supported in the 2.6[8] and later versions of the kernel. Beagle and Dropbox do use extended attributes, and freedesktop.org published recommendations[9] for their use.

For ext2/3/4 and btrfs, each extended attribute is limited to a filesystem block (e.g. 4 KiB), and in practice in ext2/3/4 all of them must fit together on a single block (including names and values). ReiserFS allow attributes of arbitrary size. In XFS the names can be up to 256 bytes in length, terminated by the first 0 byte, and the values can be up to 64KB of arbitrary binary data.

Extended attributes can be accessed and modified using the 'attr' command on most distributions.[10]

OS X[edit]

Mac OS X 10.4 and later support extended attributes by making use of the HFS+ filesystem Attributes file B*-tree feature which allows for named forks. Although the named forks in HFS+ support arbitrarily large amounts of data through extents, the OS support for extended attributes only supports inline attributes, limiting their size to that which can fit within a single B*-tree node.[citation needed] Any regular file may have a list of extended attributes. HFS+ supports an arbitrary number of named forks, and it is unknown if OS X imposes any limit on the number of extended attributes. Each attribute consists of a name and the associated data. The name is a null-terminated Unicode string. The Mac OS X APIs support listing,[11] getting,[12] setting,[13] and removing[14] extended attributes from files or directories. The xattr utility may be used from the Terminal as well.[15] Since MacOS 10.6, user space extended attributes are not preserved on save in common Cocoa applications (TextEdit, Preview etc.).[citation needed]

OS/2[edit]

In OS/2 version 1.2 and later, the High Performance File System was designed with extended attributes in mind, but support for them was also retro-fitted on the FAT filesystem of DOS. For compatibility with other operating systems using a FAT partition, OS/2 attributes are stored inside a single file "EA DATA. SF" located in the root directory. This file is normally inaccessible when an operating system supporting extended attributes manages the disk, but can be freely manipulated under, for example, DOS. Files and directories having extended attributes use one or more clusters inside this file. The logical cluster number of the first used cluster is stored inside the owning file's or directory's directory entry. These two bytes are used for other purposes on the FAT32 filesystem, and hence OS/2 extended attributes cannot be stored on this filesystem.

Parts of OS/2 version 2.0 and later such as the Workplace Shell uses several standardized extended attributes (also called EAs) for purposes like identifying the filetype, comments, computer icons and keywords about the file. Programs written in the interpreted language Rexx store an already parsed version of the code as an extended attribute, to allow faster execution.

Solaris[edit]

The Solaris operating system version 9 and later allows files to have "extended attributes", which are actually forks; the maximum size of an "extended attribute" is the same as the maximum size of a file, and they are read and written in the same fashion as files. Internally, they are actually stored and accessed like normal files, so their names cannot contain "/" characters and their ownership and permissions can differ from those of the parent file.

Version 4 of the Network File System supports extended attributes in much the same way as Solaris.

Windows NT[edit]

On Windows NT, limited-length extended attributes are supported by FAT, HPFS, and NTFS. This was implemented as part of the OS/2 subsystem. They are notably used by the NFS server of the Interix POSIX subsystem in order to implement Unix-like permissions.

Additionally, NTFS can support infinite-length extended attributes in the form of Alternate Data Streams (ADS), a type of resource fork.

See also[edit]

References[edit]

  1. ^ getea CommandAIX Commands
  2. ^ getea SubroutineAIX Technical Reference: Base Operating System and Extensions, Volume 1
  3. ^ setea SubroutineAIX Technical Reference: Base Operating System and Extensions, Volume 2
  4. ^ listea SubroutineAIX Technical Reference: Base Operating System and Extensions, Volume 1
  5. ^ statea SubroutineAIX Technical Reference: Base Operating System and Extensions, Volume 2
  6. ^ removeea SubroutineAIX Technical Reference: Base Operating System and Extensions, Volume 2
  7. ^ extattr(2) – FreeBSD System Calls Manual
  8. ^ "Red Hat Enterprise Linux AS 3 Release Notes (x86 Edition)". Red Hat. 2003. Retrieved 2013-04-08. "EA (Extended Attributes) and ACL (Access Control Lists) functionality is now available for ext3 file systems. In addition, ACL functionality is available for NFS." 
  9. ^ "Guidelines for extended attributes". 2009-08-21. Archived from the original on 2012-02-04. Retrieved 2013-04-08. 
  10. ^ "Introduction to attr". Beyond Linux From Scratch. 2013-03-04. Retrieved 2013-04-08. 
  11. ^ listxattr(2) – Darwin and Mac OS X System Calls Manual
  12. ^ getxattr(2) – Darwin and Mac OS X System Calls Manual
  13. ^ setxattr(2) – Darwin and Mac OS X System Calls Manual
  14. ^ removexattr(2) – Darwin and Mac OS X System Calls Manual
  15. ^ xattr(1) – Darwin and Mac OS X General Commands Manual

External links[edit]