Lines Matching full:filesystem
7 filesystem, such as block counts, inode counts, supported features,
140 refuse to mount the filesystem.
186 - Directory where filesystem was last mounted.
209 - Number of reserved GDT entries for future filesystem expansion.
263 - When the filesystem was created, in seconds since the epoch.
303 of filesystem metadata, which will hopefully make RAID storage faster.
309 have mounted the filesystem, in order to prevent multiple mounts. This
341 - Number of KiB written to this filesystem over its lifetime.
537 The filesystem creator is one of the following:
571 Note that ``EXT4_DYNAMIC_REV`` refers to a revision 1 or newer filesystem.
594 - Has reserved GDT blocks for filesystem expansion
641 - Filesystem needs recovery (INCOMPAT_RECOVER).
643 - Filesystem has a separate journal device (INCOMPAT_JOURNAL_DEV).
648 - Files in this filesystem use extents (INCOMPAT_EXTENTS).
650 - Enable a filesystem size of 2^64 blocks (INCOMPAT_64BIT).
663 the administrator to change the UUID of a metadata_csum filesystem
664 while the filesystem is mounted; without it, the checksum definition
674 - Encrypted inodes are present on the filesystem. (INCOMPAT_ENCRYPT).
691 - This filesystem has been used to store a file greater than 2GiB
696 - This filesystem has files whose sizes are represented in units of
708 - Indicates that large inodes exist on this filesystem
711 - This filesystem has a snapshot (RO_COMPAT_HAS_SNAPSHOT).
715 - This filesystem supports “bigalloc”, which means that file extents are
719 - This filesystem supports metadata checksumming.
723 - Filesystem supports replicas. This feature is neither in the kernel nor
726 - Read-only filesystem image; the kernel will not mount this image
730 - Filesystem tracks project quotas. (RO_COMPAT_PROJECT)
732 - Verity inodes may be present on the filesystem. (RO_COMPAT_VERITY)
735 to clean them up when mounting the filesystem
794 - Track which blocks in a filesystem are metadata and therefore should not