Searched refs:superblock (Results 51 – 69 of 69) sorted by relevance
123
/openbmc/linux/Documentation/filesystems/ |
H A D | fscrypt.rst | 656 support for filesystems, or the filesystem superblock has not 659 kernel config, and the superblock must have had the "encrypt" 715 support for this filesystem, or the filesystem superblock has not 746 generated 16-byte value stored in the filesystem superblock. This 879 support for this filesystem, or the filesystem superblock has not 1024 support for this filesystem, or the filesystem superblock has not 1102 support for this filesystem, or the filesystem superblock has not
|
H A D | xfs-self-describing-metadata.rst | 206 information, such as the superblock and AG headers. 241 by checking the superblock of the feature bit, and then if the CRC verifies OK
|
H A D | squashfs.rst | 74 | superblock |
|
H A D | fsverity.rst | 182 support; or the filesystem superblock has not had the 'verity' 230 support, or the filesystem superblock has not had the 'verity' 308 support, or the filesystem superblock has not had the 'verity'
|
H A D | erofs.rst | 293 xattr_prefix_count (of the on-disk superblock) indicates the total number of
|
H A D | xfs-online-fsck-design.rst | 535 The superblock summary counters have special requirements due to the underlying 1489 maintain summaries of this information in the superblock. 3068 but this is a slow process, so XFS maintains a copy in the ondisk superblock 3075 It is therefore only necessary to serialize on the superblock when the 3076 superblock is being committed to disk. 3135 | last reference to the VFS superblock, and any subsequent access | 3140 | superblock, but it felt suboptimal given the other inadequacies of | 4027 in the superblock protects these new log item records from being replayed on 4038 | Starting with XFS v5, the superblock contains a | 4044 | Unlike the other superblock feature bits, log incompat bits are | [all …]
|
H A D | idmappings.rst | 607 superblock. The only way to change ownership is to completely unmount the 632 advantage that filesystems can leave the creation of the superblock to
|
H A D | sharedsubtree.rst | 143 mount: wrong fs type, bad option, bad superblock on /mnt,
|
H A D | f2fs.rst | 517 F2FS splits the entire volume into six areas, and all the areas except superblock
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | ext4.rst | 247 override the errors behavior specified in the superblock, which can be 270 Use alternate superblock at this location. 490 ext4 superblock
|
H A D | xfs.rst | 42 attributes) the on-disk superblock feature bit field will be
|
/openbmc/linux/fs/affs/ |
H A D | Changes | 246 - Split inode.c into 2 files, the superblock
|
/openbmc/linux/Documentation/core-api/ |
H A D | watch_queue.rst | 98 notifications. A list may be attached to an object (say a key or a superblock)
|
/openbmc/linux/Documentation/filesystems/nfs/ |
H A D | exporting.rst | 77 per-superblock list (->s_roots), so they can be located at umount
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-fs-f2fs | 456 Description: Show status of f2fs superblock in real time. 464 0x10 SBI_NEED_SB_WRITE need to recover superblock
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | cache.rst | 286 superblock. The metadata device must be
|
H A D | thin-provisioning.rst | 347 flag being set in the metadata's superblock. The metadata
|
/openbmc/linux/drivers/md/ |
H A D | dm-integrity.c | 68 struct superblock { struct 174 struct superblock *sb; 500 if (sizeof(struct superblock) + size > 1 << SECTOR_SHIFT) { in sb_mac()
|
H A D | Kconfig | 60 bitmaps near the MD superblock, and very problematic code that abuses
|
123