Searched full:filesystem (Results 1 – 25 of 2342) sorted by relevance
12345678910>>...94
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | fuse.rst | 10 Userspace filesystem:
11 A filesystem in which data and metadata are provided by an ordinary
12 userspace process. The filesystem can be accessed normally through
15 Filesystem daemon:
16 The process(es) providing the data and metadata of the filesystem.
19 A userspace filesystem mounted by a non-privileged (non-root) user.
20 The filesystem daemon is running with the privileges of the mounting
24 Filesystem connection:
25 A connection between the filesystem daemon and the kernel. The
26 connection exists until either the daemon dies, or the filesystem is
[all …]
|
| D | overlayfs.rst | 6 Overlay Filesystem
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
12 filesystem which is the result over overlaying one filesystem on top
19 The overlay filesystem approach is 'hybrid', because the objects that
20 appear in the filesystem do not always appear to belong to that filesystem.
22 from accessing the corresponding object from the original filesystem.
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
27 upper filesystem that is providing the object. Similarly st_ino will
[all …]
|
| D | ext2.rst | 4 The Second Extended Filesystem
9 Extended Filesystem. It is currently still (April 2001) the predominant
10 filesystem in use by Linux. There are also implementations available
16 Most defaults are determined by the filesystem superblock, and can be
32 errors=continue Keep going on a filesystem error.
33 errors=remount-ro Remount the filesystem read-only on an error.
89 which is decided when the filesystem is created. Smaller blocks mean
91 and also impose other limits on the size of files and the filesystem.
116 to mounting the filesystem. Since it is so important, backup copies of
117 the superblock are stored in block groups throughout the filesystem.
[all …]
|
| D | mount_api.rst | 4 Filesystem Mount API
11 (2) The filesystem context.
13 (3) The filesystem context operations.
15 (4) Filesystem context security.
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
57 Note that security initialisation is done *after* the filesystem is called so
61 The Filesystem context
64 The creation and reconfiguration of a superblock is governed by a filesystem
[all …]
|
| D | autofs.rst | 23 filesystem can even be programmatic rather than database-backed,
30 The "autofs" filesystem module is only one part of an autofs system.
39 filesystem type. Several "autofs" filesystems can be mounted and they
45 An autofs filesystem can contain 3 sorts of objects: directories,
62 directory is a mount trap only if the filesystem is mounted *direct*
66 filesystem is mounted *indirect* and they are empty.
85 filesystem can be designated as a trap. This involves two separate
94 to be called. The task of this method is to find the filesystem that
96 responsible for actually mounting the root of this filesystem on the
99 autofs doesn't find the filesystem itself but sends a message to the
[all …]
|
| D | qnx6.rst | 4 The QNX6 Filesystem
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)
86 The inode structure contains pointers to the filesystem blocks which contain
[all …]
|
| 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
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | fuse.rst | 10 Userspace filesystem:
11 A filesystem in which data and metadata are provided by an ordinary
12 userspace process. The filesystem can be accessed normally through
15 Filesystem daemon:
16 The process(es) providing the data and metadata of the filesystem.
19 A userspace filesystem mounted by a non-privileged (non-root) user.
20 The filesystem daemon is running with the privileges of the mounting
24 Filesystem connection:
25 A connection between the filesystem daemon and the kernel. The
26 connection exists until either the daemon dies, or the filesystem is
[all …]
|
| D | idmappings.rst | 6 Most filesystem developers will have encountered idmappings. They are used when
8 for permission checking. This document is aimed at filesystem developers that
157 outside of the filesystem context. This is best left to an explanation of user
173 ownership of a file is read from disk by a filesystem, the userspace id is
177 For instance, consider a file that is stored on disk by a filesystem as being
180 - If a filesystem were to be mounted in the initial user namespaces (as most
186 - If a filesystem were to be mounted with an idmapping of ``u0:k10000:r10000``
233 into a kernel id according to the idmapping associated with the filesystem.
234 Let's assume the filesystem was mounted with an idmapping of
241 according to the filesystem's idmapping as this would give the wrong owner if
[all …]
|
| D | overlayfs.rst | 6 Overlay Filesystem
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
12 filesystem which is the result over overlaying one filesystem on top
19 The overlay filesystem approach is 'hybrid', because the objects that
20 appear in the filesystem do not always appear to belong to that filesystem.
22 from accessing the corresponding object from the original filesystem.
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
27 upper filesystem that is providing the object. Similarly st_ino will
[all …]
|
| D | ext2.rst | 5 The Second Extended Filesystem
10 Extended Filesystem. It is currently still (April 2001) the predominant
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
90 and also impose other limits on the size of files and the filesystem.
115 to mounting the filesystem. Since it is so important, backup copies of
116 the superblock are stored in block groups throughout the filesystem.
[all …]
|
| D | mount_api.rst | 4 Filesystem Mount API
11 (2) The filesystem context.
13 (3) The filesystem context operations.
15 (4) Filesystem context security.
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
57 Note that security initialisation is done *after* the filesystem is called so
61 The Filesystem context
64 The creation and reconfiguration of a superblock is governed by a filesystem
[all …]
|
| D | autofs.rst | 23 filesystem can even be programmatic rather than database-backed,
30 The "autofs" filesystem module is only one part of an autofs system.
39 filesystem type. Several "autofs" filesystems can be mounted and they
45 An autofs filesystem can contain 3 sorts of objects: directories,
62 directory is a mount trap only if the filesystem is mounted *direct*
66 filesystem is mounted *indirect* and they are empty.
85 filesystem can be designated as a trap. This involves two separate
94 to be called. The task of this method is to find the filesystem that
96 responsible for actually mounting the root of this filesystem on the
99 autofs doesn't find the filesystem itself but sends a message to the
[all …]
|
| D | qnx6.rst | 4 The QNX6 Filesystem
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)
86 The inode structure contains pointers to the filesystem blocks which contain
[all …]
|
| 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
|
| /kernel/linux/linux-6.6/fs/ext4/ |
| 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"
39 This is the next generation of the ext3 filesystem.
41 Unlike the change from ext2 filesystem to ext3 filesystem,
44 physical block numbers. The ext4 filesystem also supports delayed
50 The ext4 filesystem supports mounting an ext3 filesystem; while there
53 features in the filesystem using tune2fs, or formatting a new
[all …]
|
| /kernel/linux/linux-5.10/fs/ext4/ |
| 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,
43 physical block numbers. The ext4 filesystem also supports delayed
49 The ext4 filesystem supports mounting an ext3 filesystem; while there
52 features in the filesystem using tune2fs, or formatting a new
[all …]
|
| /kernel/linux/linux-6.6/fs/xfs/ |
| 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
38 xfs_info against a filesystem mountpoint and checking for a string
40 filesystem is a V4 filesystem. If no such string is found, please
55 The ASCII case insensitivity filesystem feature only works correctly
64 Administrators and users can detect such a filesystem by running
65 xfs_info against a filesystem mountpoint and checking for a string
67 filesystem is a case-insensitive filesystem. If no such string is
[all …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/nfs/ |
| 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.
98 Filesystem Issues
[all …]
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| 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
38 xfs_info against a filesystem mountpoint and checking for a string
40 filesystem is a V4 filesystem. If no such string is found, please
57 information as filesystem metadata and uses journaling to provide a
60 filesystem to be migrated between Linux and IRIX without any need
102 mounted XFS filesystem. This feature is intended to reduce
103 filesystem downtime by supplementing xfs_repair. The key
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | xfs.rst | 4 The SGI XFS Filesystem
7 XFS is a high performance journaling filesystem which originated
22 When mounting an XFS filesystem, the following options are accepted.
48 by the filesystem.
55 device reclaim space freed by the filesystem. This is
75 across the entire filesystem rather than just on directories
90 to create inodes at any location in the filesystem,
108 If ``largeio`` is specified, a filesystem that was created with a
110 in ``st_blksize``. If the filesystem does not have a ``swidth``
141 An XFS filesystem has up to three parts: a data section, a log
[all …]
|
| D | ext4.rst | 7 Ext4 is an advanced level of the ext3 filesystem which incorporates
35 - Create a new filesystem using the ext4 filesystem type:
39 Or to configure an existing ext3 filesystem to support extents:
43 If the filesystem was created with 128 byte inodes, it can be
66 the filesystem with a large journal can also be helpful for
106 case-sensitive directories in the same filesystem. It is enabled by
110 case-insensitive directories, the filesystem must have the
111 casefold feature, which stores the filesystem-wide encoding
132 filesystem, which select its preferred behavior by enabling/disabling
134 filesystem did not require strict mode, it falls back to considering the
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | ext4.rst | 7 Ext4 is an advanced level of the ext3 filesystem which incorporates
35 - Create a new filesystem using the ext4 filesystem type:
39 Or to configure an existing ext3 filesystem to support extents:
43 If the filesystem was created with 128 byte inodes, it can be
66 the filesystem with a large journal can also be helpful for
106 case-sensitive directories in the same filesystem. It is enabled by
110 case-insensitive directories, the filesystem must have the
111 casefold feature, which stores the filesystem-wide encoding
132 filesystem, which select its preferred behavior by enabling/disabling
134 filesystem did not require strict mode, it falls back to considering the
[all …]
|
| D | xfs.rst | 4 The SGI XFS Filesystem
7 XFS is a high performance journaling filesystem which originated
22 When mounting an XFS filesystem, the following options are accepted.
48 by the filesystem.
55 device reclaim space freed by the filesystem. This is
75 across the entire filesystem rather than just on directories
90 to create inodes at any location in the filesystem,
108 If ``largeio`` is specified, a filesystem that was created with a
110 in ``st_blksize``. If the filesystem does not have a ``swidth``
141 An XFS filesystem has up to three parts: a data section, a log
[all …]
|
| /kernel/linux/linux-6.6/fs/ |
| D | mnt_idmapping.c | 31 * @sb: super block of the filesystem
58 * @fs_userns: the filesystem's idmapping
65 * filesystem are identical no remapping is required.
76 * make_vfsuid - map a filesystem kuid according to an idmapping
78 * @fs_userns: the filesystem's idmapping
86 * If initial_idmapping() tells us that the filesystem is not mounted with an
116 * make_vfsgid - map a filesystem kgid according to an idmapping
118 * @fs_userns: the filesystem's idmapping
126 * If initial_idmapping() tells us that the filesystem is not mounted with an
154 * from_vfsuid - map a vfsuid into the filesystem idmapping
[all …]
|
12345678910>>...94