Home Explore Blog CI



man-pages

2nd chunk of `chattr.man`
9fcd31d2a2647f4546eda87696d1e4d5c500004a730338810000000100000e5a
 btrfs, the ’C’ flag should be set on new or
              empty files.  If it is set on a file which already has data blocks, it is undefined when the blocks assigned to the file will be fully stable.  If the ’C’ flag is set on a directory, it will have no  effect  on
              the directory, but new files created in that directory will have the No_COW attribute set. If the ’C’ flag is set, then the ’c’ flag cannot be set.)

       d      A file with the ’d’ attribute set is not a candidate for backup when the dump(8) program is run.

       D      When a directory with the ’D’ attribute set is modified, the changes are written synchronously to the disk; this is equivalent to the ’dirsync’ mount option applied to a subset of the files.

       e      The ’e’ attribute indicates that the file is using extents for mapping the blocks on disk.  It may not be removed using chattr(1).

       E      A file, directory, or symlink with the ’E’ attribute set is encrypted by the file system.  This attribute may not be set or cleared using chattr(1), although it can be displayed by lsattr(1).

       F      A  directory with the ’F’ attribute set indicates that all the path lookups inside that directory are made in a case‐insensitive fashion.  This attribute can only be changed in empty directories on file systems
              with the casefold feature enabled.

       i      A file with the ’i’ attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file, most of the file’s metadata can not be modified, and the file can not be opened  in  write
              mode.  Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.

       I      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 cleared using chattr(1), although it can be displayed by lsattr(1).

       j      A  file  with the ’j’ attribute has all of its data written to the ext3 or ext4 journal before being written to the file itself, if the file system is mounted with the "data=ordered" or "data=writeback" options
              and the file system has a journal.  When the file system 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 possess‐
              ing the CAP_SYS_RESOURCE capability can set or clear this attribute.

       m      A file with the ’m’ attribute is excluded from compression on file systems that support per‐file compression.

       N      A file with the ’N’ attribute set indicates that the file has data stored inline, within the inode itself. It may not be set or cleared using chattr(1), although it can be displayed by lsattr(1).

       P      A directory with the ’P’ attribute set will enforce a hierarchical structure for project id’s.  This means that files and directories created in the directory will inherit the project id of the  directory,  re‐
              name  operations  are  constrained so when a file or directory is moved into another directory, that the project ids must match.  In addition, a hard link to file can only be created when the project id for the
              file and the destination directory match.

       s      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.

       S      When a file with the ’S’ attribute

Title: chattr Attributes Continued
Summary
This section continues the description of the attributes that can be set or viewed using the `chattr` and `lsattr` commands. It details the function of attributes such as 'd' (no backup), 'D' (synchronous directory updates), 'e' (extent format), 'E' (encrypted), 'F' (case-insensitive directory lookups), 'i' (immutable), 'I' (indexed directory), 'j' (journaled data), 'm' (no compression), 'N' (inline data), 'P' (project hierarchy), and 's' (secure deletion).