Which statement is true about Linux Extended Attributes on files? (Select 2 correct answers)

Which statement is true about Linux Extended Attributes on files? (Select 2 correct answers)

• A. An attribute value may be empty
• B. Attribute storage counts towards disk quota use
• C. Attribute use is enabled by mounting a partition with the attr option
• D. An attribute is file, not inode, specific

Answer: (A)

The assertion that an attribute value may be empty is indeed true. Extended Attributes (EAs) in Linux allow users to associate additional metadata with files beyond the standard attributes such as ownership and permissions. These attributes can indeed be empty; if an attribute is set but has no value assigned to it, it can still be valid. This feature enables flexibility in managing file metadata without enforcing a mandatory value requirement. In addition, the statement concerning the storage of attributes counting towards disk quota use is also true. When a filesystem supports extended attributes, the space used by these attributes is accounted for in the overall disk quota allocated to the user or group. This is important for storage management, ensuring that users are aware that their usage extends beyond just the file size to include any associated metadata stored as extended attributes. While using the attr option during the mounting of a partition does enable the functionality of extended attributes, it is not solely dependent on that setting for their use; many filesystems already have support for EAs built-in. Similarly, attributes in Linux are tied to the file inode rather than being file-specific; they are more accurately described as being associated with inodes, allowing for unified management of attribute values across hard links and file modifications.

The assertion that an attribute value may be empty is indeed true. Extended Attributes (EAs) in Linux allow users to associate additional metadata with files beyond the standard attributes such as ownership and permissions. These attributes can indeed be empty; if an attribute is set but has no value assigned to it, it can still be valid. This feature enables flexibility in managing file metadata without enforcing a mandatory value requirement.

In addition, the statement concerning the storage of attributes counting towards disk quota use is also true. When a filesystem supports extended attributes, the space used by these attributes is accounted for in the overall disk quota allocated to the user or group. This is important for storage management, ensuring that users are aware that their usage extends beyond just the file size to include any associated metadata stored as extended attributes.

While using the attr option during the mounting of a partition does enable the functionality of extended attributes, it is not solely dependent on that setting for their use; many filesystems already have support for EAs built-in. Similarly, attributes in Linux are tied to the file inode rather than being file-specific; they are more accurately described as being associated with inodes, allowing for unified management of attribute values across hard links and file modifications.