A little known aspect of the Linux file system is file attributes. They allow you to utilize certain options which you might think you need other software for, but they’re actually built into your file system. To view or change these you can use the lsattr and chattr commands. The available attributes are:<\/p>\n
When a file with the ‘A’ attribute set is accessed, its atime record is not modified. This avoids a certain amount of disk I\/O for laptop systems.<\/p>\n
A file with the `a’ attribute set can only be open in append mode for writing. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.<\/p>\n
A file with the `c’ attribute set is automatically compressed on the disk by the kernel. A read from this file returns uncompressed data. A write to this file compresses data before storing them on the disk. Note: please make sure to read the bugs and limitations section at the end of this document.<\/p>\n
When a directory with the `D’ attribute set is modified, the changes are written synchronously on the disk; this is equivalent to the `dirsync’ mount option applied to a subset of the files.<\/p>\n
A file with the `d’ attribute set is not candidate for backup when the dump(8) program is run.<\/p>\n
The ‘E’ attribute is used by the experimental compression patches to indicate that a compressed file has a compression error. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1).<\/p>\n
The ‘e’ attribute indicates that the file is using extents for mapping the blocks on disk. It may not be removed using chattr(1).<\/p>\n
The ‘I’ attribute is used by the htree code to indicate that a directory is being indexed using hashed trees. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1).<\/p>\n
The ‘h’ attribute indicates the file is storing its blocks in units of the filesystem blocksize instead of in units of sectors, and means that the file is (or at one time was) larger than 2TB. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1).<\/p>\n
A file with the `i’ attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file and no data can be written to the file. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.<\/p>\n
A file with the `j’ attribute has all of its data written to the ext3 journal before being written to the file itself, if the filesystem is mounted with the “data=ordered” or “data=writeback” options. When the filesystem is mounted with the “data=journal” option all file data is already journalled and this attribute has no effect. Only the superuser or a process possessing the CAP_SYS_RESOURCE capability can set or clear this attribute.<\/p>\n
When a file with the `s’ attribute set is deleted, its blocks are zeroed and written back to the disk. Note: please make sure to read the bugs and limitations section at the end of this document.<\/p>\n
When a file with the `S’ attribute set is modified, the changes are written synchronously on the disk; this is equivalent to the `sync’ mount option applied to a subset of the files.<\/p>\n
A directory with the ‘T’ attribute will be deemed to be the top of directory hierarchies for the purposes of the Orlov block allocator. This is a hint to the block allocator used by ext3 and ext4 that the subdirectories under this directory are not related, and thus should be spread apart for allocation purposes. For example it is a very good idea to set the ‘T’ attribute on the \/home directory, so that \/home\/john and \/home\/mary are placed into separate block groups. For directories where this attribute is not set, the Orlov block allocator will try to group subdirectories closer
\ntogether where possible.<\/p>\n
A file with the ‘t’ attribute will not have a partial block fragment at the end of the file merged with other files (for those filesystems which support tail-merging). This is necessary for applications such as LILO which read the filesystem directly, and which don’t understand tail-merged files. Note: As of this writing, the ext2 or ext3 filesystems do not (yet, except in very experimental patches) support tail-merging.<\/p>\n
When a file with the `u’ attribute set is deleted, its contents are saved. This allows the user to ask for its undeletion. Note: please make sure to read the bugs and limitations section at the end of this document.<\/p>\n
The ‘X’ attribute is used by the experimental compression patches to indicate that a raw contents of a compressed file can be accessed directly. It currently may not be set or reset using chattr(1), although it can be displayed by lsattr(1).<\/p>\n
The ‘Z’ attribute is used by the experimental compression patches to indicate a compressed file is dirty. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1).<\/p>\n","protected":false},"excerpt":{"rendered":"
A little known aspect of the Linux file system is file attributes. They allow you to utilize certain options which you might think you need other software for, but they’re actually built into your file system. To view or change these you can use the lsattr and chattr commands. The available attributes are: When a… <\/p>\n