| /linux-6.15/Documentation/filesystems/ |
| H A D | fuse.rst | 10 Userspace filesystem:
106 Control filesystem
125 filesystem is hung or deadlocked.
134 Interrupting filesystem operations
174 Aborting a filesystem connection
195 - Kill the filesystem daemon and all users of the filesystem. Works
201 - Abort filesystem through the FUSE control filesystem. Most
215 help of the mounted filesystem
238 filesystem, the filesystem daemon serving requests can record the
279 the filesystem or not.
[all …]
|
| H A D | idmappings.rst | 363 filesystem's idmapping.
375 filesystem's idmapping.
405 filesystem's idmapping.
431 filesystem's idmapping::
459 filesystem's idmapping::
615 filesystem images.
685 on filesystem idmappings. To prevent abusing filesystem idmappings to generate
709 /* Map the filesystem's kernel id up into a userspace id in the filesystem's idmapping. */
825 filesystem's idmapping::
858 filesystem's idmapping::
[all …]
|
| H A D | ext2.rst | 11 filesystem in use by Linux. There are also implementations available
17 Most defaults are determined by the filesystem superblock, and can be
33 errors=continue Keep going on a filesystem error.
34 errors=remount-ro Remount the filesystem read-only on an error.
88 which is decided when the filesystem is created. Smaller blocks mean
116 the superblock are stored in block groups throughout the filesystem.
170 and changed with the chattr command, and allow specific filesystem
236 It safely allows features to be added to the filesystem, without
249 the filesystem without any chance of corrupting the filesystem (or even
260 filesystem would/could corrupt the filesystem, so this is prevented. The
[all …]
|
| H A D | overlayfs.rst | 12 filesystem which is the result over overlaying one filesystem on top
20 appear in the filesystem do not always appear to belong to that filesystem.
34 filesystem and st_ino from the underlying filesystem. This will
37 objects in the original filesystem.
86 An overlay filesystem combines two filesystems - an 'upper' filesystem
107 filesystem type.
144 filesystem, an overlay filesystem needs to record in the upper filesystem
590 filesystem.
605 compliant filesystem:
639 overlay filesystem and the value of st_ino for filesystem objects may not be
[all …]
|
| H A D | mount_api.rst | 11 (2) The filesystem context.
13 (3) The filesystem context operations.
17 (5) VFS filesystem context API.
31 (1) Create a filesystem context.
52 The first is invoked to set up the filesystem-specific parts of a filesystem
222 manage the filesystem context. They are as follows:
228 Called to clean up the filesystem-specific part of the filesystem context
244 filesystem-private data safe for ->free().
443 filesystem type as fs_type.
463 created a filesystem context.
[all …]
|
| H A D | ocfs2-online-filecheck.rst | 12 converts the filesystem to read-only when encounters an error. This may not be
13 necessary, since turning the filesystem read-only would affect other running
17 filesystem is not corrupted further. The filesystem is not converted to
24 of a cluster filesystem by turning the filesystem read-only. The scope of
26 to all files (including system files) of the filesystem.
32 other components of the filesystem, such as but not limited to, checking if the
36 Finally, such an operation/feature should not be automated lest the filesystem
42 When there are errors in the OCFS2 filesystem, they are usually accompanied
91 On receiving the inode, the filesystem would read the inode and the
92 file metadata. In case of errors, the filesystem would fix the errors
|
| H A D | hfs.rst | 8 .. Note:: This filesystem doesn't have a maintainer.
11 HFS stands for ``Hierarchical File System`` and is the filesystem used
14 MacOS 8.1 and newer support a filesystem called HFS+ that's similar to
15 HFS but is extended in various areas. Use the hfsplus filesystem driver
22 When mounting an HFS filesystem, the following options are accepted:
37 Select the CDROM session to mount as HFS filesystem. Defaults to
54 HFS is not a UNIX filesystem, thus it does not have the usual features you'd
70 * Copying files to a different filesystem will loose those attributes
78 hformat that can be used to create HFS filesystem. See
|
| H A D | gfs2-uevents.rst | 18 uevent generated by the newly created filesystem. If the mount
25 of the filesystem respectively.
40 successful mount of the filesystem by the first node (FIRSTMOUNT=Done).
42 nodes in the cluster to mount the filesystem.
63 The OFFLINE uevent is only generated due to filesystem errors and is used
72 or at the end of a umount of the filesystem. All REMOVE uevents will
73 have been preceded by at least an ADD uevent for the same filesystem,
85 line (locktable=) or via fstab. It is used as a filesystem label
100 If a journal is in use by the filesystem (journals are not
108 into the filesystem superblock. If it exists, this will
[all …]
|
| H A D | directory-locking.rst | 7 kinds of locks - per-inode (->i_rwsem) and per-filesystem
55 * lock the filesystem
114 Multiple-filesystem stuff
119 filesystem, overlayfs doing something to the layers, network filesystem
127 filesystem ranks lower than whatever it caches on, etc.)
145 on the same filesystem.
151 1. ->s_vfs_rename_mutex of NFS filesystem
153 3. ->i_rwsem of non-directories on that filesystem, in order of
155 4. ->s_vfs_rename_mutex of local filesystem
157 6. ->i_rwsem of non-directories on local filesystem, in order of
[all …]
|
| H A D | qnx6.rst | 13 mmi_fs Mount filesystem as used for example by Audi MMI 3G system
32 size of 512, 1024, 2048 or 4096, which is decided when the filesystem is
41 The superblock contains all global information about the filesystem.
50 (or period) and building up a new (stable) filesystem structure under the
53 Each superblock holds a set of root inodes for the different filesystem
75 information (total number of filesystem blocks) or by taking the highest
80 blocksize of the filesystem.
85 Each object in the filesystem is represented by an inode. (index node)
106 A directory is a filesystem object and has an inode just like a file.
138 underlying filesystem.
[all …]
|
| H A D | autofs.rst | 23 filesystem can even be programmatic rather than database-backed,
45 An autofs filesystem can contain 3 sorts of objects: directories,
66 filesystem is mounted *indirect* and they are empty.
129 expiry (automatic unmounting of the mounted filesystem) to
195 mounted filesystem, otherwise it should return 0.
310 When an autofs filesystem is mounted the pgid of the mounting
397 the filesystem could be unmounted. This is only a hint as
489 on the root of an autofs filesystem. The filesystem is identified
496 if the filesystem is in
503 name within the filesystem that has been auto-mounted on.
[all …]
|
| H A D | gfs2.rst | 46 fsck.gfs2 to repair a filesystem
47 gfs2_grow to expand a filesystem online
48 gfs2_jadd to add journals to a filesystem online
49 tunegfs2 to manipulate, examine and tune a filesystem
50 gfs2_convert to convert a gfs filesystem to GFS2 in-place
51 mkfs.gfs2 to make a filesystem
|
| /linux-6.15/fs/ext4/ |
| H A D | Kconfig | 6 tristate "The Extended 3 (ext3) filesystem"
10 filesystem is now handled by the ext4 driver.
19 filesystem is now handled by the ext4 driver.
27 filesystem is now handled by the ext4 driver.
30 tristate "The Extended 4 (ext4) filesystem"
38 This is the next generation of the ext3 filesystem.
40 Unlike the change from ext2 filesystem to ext3 filesystem,
49 The ext4 filesystem supports mounting an ext3 filesystem; while there
53 filesystem as an ext4 filesystem initially. Without explicit enabling
90 labels in the ext4 filesystem.
[all …]
|
| /linux-6.15/Documentation/filesystems/ext4/ |
| H A D | mmp.rst | 7 filesystem against multiple hosts trying to use the filesystem
8 simultaneously. When a filesystem is opened (for mounting, or fsck,
15 filesystem is active on another machine and the open fails. If the MMP
19 While the filesystem is live, the kernel sets up a timer to re-check the
23 filesystem, and node A remounts the filesystem read-only. If the
57 - Hostname of the node that opened the filesystem.
61 - Block device name of the filesystem.
|
| H A D | orphan.rst | 7 are still alive because they are open. In case of crash the filesystem has to
17 inode (we overload i_dtime inode field for this). However this filesystem
20 (COMPAT_ORPHAN_FILE) is enabled, the filesystem has a special inode
36 When a filesystem with orphan file feature is writeably mounted, we set
39 filesystem, we read the whole orphan file and process all orphan inodes found
40 there as usual. When cleanly unmounting the filesystem we remove the
42 file and also make the filesystem fully compatible with older kernels.
|
| /linux-6.15/fs/xfs/ |
| H A D | Kconfig | 3 tristate "XFS filesystem support"
9 XFS is a high performance journaling filesystem which originated
30 The V4 filesystem format lacks certain features that are supported
37 Administrators and users can detect a V4 filesystem by running
40 filesystem is a V4 filesystem. If no such string is found, please
67 filesystem is a case-insensitive filesystem. If no such string is
147 mounted XFS filesystem. This feature is intended to reduce
148 filesystem downtime by supplementing xfs_repair. The key
169 filesystem counters.
182 mounted XFS filesystem. This feature is intended to reduce
[all …]
|
| /linux-6.15/fs/configfs/ |
| H A D | Kconfig | 3 tristate "Userspace-driven configuration filesystem"
6 configfs is a RAM-based filesystem that provides the converse
7 of sysfs's functionality. Where sysfs is a filesystem-based
8 view of kernel objects, configfs is a filesystem-based manager
|
| /linux-6.15/Documentation/admin-guide/LSM/ |
| H A D | LoadPin.rst | 6 (modules, firmware, etc) all originate from the same filesystem, with
7 the expectation that such a filesystem is backed by a read-only device
9 and/or unchangeable filesystem to enforce module and firmware loading
18 block device backing the filesystem is not read-only, a sysctl is
20 a mutable filesystem means pinning is mutable too, but having the
21 sysctl allows for easy testing on systems with a mutable filesystem.)
|
| /linux-6.15/Documentation/filesystems/iomap/ |
| H A D | design.rst | 20 iomap is a filesystem library for handling common file operations.
25 from the filesystem, but the storage information is not necessarily
52 The target audience for this document are filesystem, storage, and
63 the basis of that unit, the iomap model asks the filesystem for the
130 * **filesystem mapping lock**: This synchronization primitive is
154 The filesystem communicates to the iomap iterator the mapping of
178 These fields must always be set by the filesystem.
247 be set by the filesystem for its own purposes.
279 * ``private`` is a pointer to `filesystem-private information
352 If there is any doubt in the filesystem developer's mind as to
[all …]
|
| /linux-6.15/Documentation/filesystems/nfs/ |
| H A D | reexport.rst | 7 It is possible to reexport an NFS filesystem over NFS. However, this
18 filesystem. You can use "uuidgen -r" to generate a unique argument.
22 filesystems mounted under the exported filesystem, you'll need to export
54 So, for example, you will only be able to reexport a filesystem over
63 filesystem, the second is the length after that nfs export is reexported
84 - If you export a subdirectory of a filesystem (instead of
85 exporting the filesystem root), that also usually adds 4 to 8
88 filesystem identifier that saves 8 bytes.
93 you're unlikely to have trouble using NFSv4 to reexport any filesystem
115 filesystem locally. A reexport server will also not pass them along to
|
| H A D | exporting.rst | 9 All filesystem operations require a dentry (or two) as a starting
12 applications that access a filesystem via a remote filesystem protocol
19 The mechanism discussed here allows each filesystem implementation to
20 specify how to generate an opaque (outside of the filesystem) byte
26 A filesystem which supports the mapping between filehandle fragments
34 The dcache normally contains a proper prefix of any given filesystem
35 tree. This means that if any filesystem object is in the dcache, then
36 all of the ancestors of that filesystem object are also in the dcache.
44 the dcache that are not needed for normal filesystem access.
101 For a filesystem to be exportable it must:
[all …]
|
| /linux-6.15/fs/overlayfs/ |
| H A D | Kconfig | 3 tristate "Overlay filesystem support"
7 An overlay filesystem combines two filesystems - an 'upper' filesystem
8 and a 'lower' filesystem. When a name exists in both filesystems, the
9 object in the 'upper' filesystem is visible while the object in the
10 'lower' filesystem is either hidden or, in the case of directories,
22 "redirect_dir=off" module option or on a filesystem instance basis
53 "index=off" module option or on a filesystem instance basis with the
74 globally with the "nfs_export=off" module option or on a filesystem
100 unused high bits in underlying filesystem inode numbers to map all
120 module option or on a filesystem instance basis with the
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | xfs.rst | 7 XFS is a high performance journaling filesystem which originated
48 by the filesystem.
55 device reclaim space freed by the filesystem. This is
90 to create inodes at any location in the filesystem,
184 within the filesystem.
221 When specified, all filesystem namespace operations are
258 Mounting with V4 filesystem September 2030
259 Mounting ascii-ci filesystem September 2030
289 The interval at which the filesystem flushes metadata
431 mounted filesystem:
[all …]
|
| /linux-6.15/fs/gfs2/ |
| H A D | Kconfig | 10 A cluster filesystem.
14 and writes to the block device like a local filesystem, but also uses
16 filesystem consistency is maintained. One of the nifty features of
17 GFS is perfect consistency -- changes made to the filesystem on one
20 To use the GFS2 filesystem in a cluster, you will need to enable
|
| /linux-6.15/Documentation/driver-api/firmware/ |
| H A D | direct-fs-lookup.rst | 2 Direct filesystem lookup
5 Direct filesystem lookup is the most common form of firmware lookup performed
7 filesystem in the paths documented in the section 'Firmware search paths'.
8 The filesystem lookup is implemented in fw_get_filesystem_firmware(), it
12 It is recommended you keep /lib/firmware paths on your root filesystem,
|