Searched full:filesystem (Results 1 – 25 of 1362) sorted by relevance
12345678910>>...55
| /Linux-v6.1/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 | 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
156 outside of the filesystem context. This is best left to an explanation of user
172 ownership of a file is read from disk by a filesystem, the userspace id is
176 For instance, consider a file that is stored on disk by a filesystem as being
179 - If a filesystem were to be mounted in the initial user namespaces (as most
185 - If a filesystem were to be mounted with an idmapping of ``u0:k10000:r10000``
232 into a kernel id according to the idmapping associated with the filesystem.
233 Let's assume the filesystem was mounted with an idmapping of
240 according to the filesystem's idmapping as this would give the wrong owner if
[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
|
| D | hfs.rst | 4 Macintosh HFS Filesystem for Linux
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
|
| D | vfs.rst | 16 The Virtual File System (also known as the Virtual Filesystem Switch) is
17 the software layer in the kernel that provides the filesystem interface
19 kernel which allows different filesystem implementations to coexist.
22 are called from a process context. Filesystem locking is described in
47 filesystem objects such as regular files, directories, FIFOs and other
56 filesystem implementation that the inode lives in. Once the VFS has the
71 specific filesystem implementation can do its work. You can see that
82 Registering and Mounting a Filesystem
85 To register and unregister a filesystem, use the following API
95 The passed struct file_system_type describes your filesystem. When a
[all …]
|
| 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 …]
|
| D | fsverity.rst | 15 btrfs filesystems. Like fscrypt, not too much filesystem-specific
22 causes the filesystem to build a Merkle tree for the file and persist
23 it to a filesystem-specific location associated with the file.
69 must live on a read-write filesystem because they are independently
124 necessarily the same as the filesystem block size.
139 FS_IOC_ENABLE_VERITY causes the filesystem to build a Merkle tree for
140 the file and persist it to a filesystem-specific location associated
176 - ``ENOTTY``: this type of filesystem does not implement fs-verity
178 support; or the filesystem superblock has not had the 'verity'
179 feature enabled on it; or the filesystem does not support fs-verity
[all …]
|
| D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt)
25 Unlike dm-crypt, fscrypt operates at the filesystem level rather than
28 filesystem. This is useful for multi-user systems where each user's
30 However, except for filenames, fscrypt does not encrypt filesystem
33 Unlike eCryptfs, which is a stacked filesystem, fscrypt is integrated
66 if an attacker is able to manipulate the filesystem offline prior to
67 an authorized user later accessing the filesystem.
157 access. Because of filesystem caching, the wrong key will then be
252 filesystem's inode table, and there didn't appear to be any
288 number, and filesystem UUID. This normally results in all files
[all …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/include/linux/ |
| D | mnt_idmapping.h | 156 * @fs_userns: the filesystem's idmapping
163 * filesystem are identical no remapping is required.
174 * make_vfsuid - map a filesystem kuid into a mnt_userns
176 * @fs_userns: the filesystem's idmapping
184 * If initial_idmapping() tells us that the filesystem is not mounted with an
219 * make_vfsgid - map a filesystem kgid into a mnt_userns
221 * @fs_userns: the filesystem's idmapping
229 * If initial_idmapping() tells us that the filesystem is not mounted with an
264 * from_vfsuid - map a vfsuid into the filesystem idmapping
266 * @fs_userns: the filesystem's idmapping
[all …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/fs/overlayfs/ |
| D | Kconfig | 3 tristate "Overlay filesystem support"
6 An overlay filesystem combines two filesystems - an 'upper' filesystem
7 and a 'lower' filesystem. When a name exists in both filesystems, the
8 object in the 'upper' filesystem is visible while the object in the
9 'lower' filesystem is either hidden or, in the case of directories,
21 "redirect_dir=off" module option or on a filesystem instance basis
52 "index=off" module option or on a filesystem instance basis with the
73 globally with the "nfs_export=off" module option or on a filesystem
99 unused high bits in undelying filesystem inode numbers to map all
119 module option or on a filesystem instance basis with the
|
| /Linux-v6.1/Documentation/filesystems/ext4/ |
| 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.
|
| D | super.rst | 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
337 - Number of KiB written to this filesystem over its lifetime.
529 The filesystem creator is one of the following:
563 Note that ``EXT4_DYNAMIC_REV`` refers to a revision 1 or newer filesystem.
[all …]
|
| /Linux-v6.1/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 4 Network Filesystem Caching API
7 Fscache provides an API by which a network filesystem can make use of local
45 The fscache hierarchy is organised on two levels from a network filesystem's
50 A network filesystem acquires a volume cookie for a volume using a volume key,
58 A filesystem would typically have a volume cookie for each superblock.
60 The filesystem then acquires a cookie for each file within that volume using an
65 filesystem.
67 A filesystem would typically have a cookie for each inode, and would acquire it
70 Once it has a cookie, the filesystem needs to mark the cookie as being in use.
75 A filesystem would typically "use" the cookie in its file open routine and
[all …]
|
| /Linux-v6.1/fs/fuse/ |
| D | Kconfig | 3 tristate "FUSE (Filesystem in Userspace) support"
6 With FUSE it is possible to implement a fully functional filesystem
19 a filesystem based on FUSE, answer Y or M.
32 tristate "Virtio Filesystem"
36 The Virtio Filesystem allows guests to mount file systems from the
43 bool "Virtio Filesystem Direct Host Memory Access support"
53 If you want to allow mounting a Virtio Filesystem with the "dax"
|
| /Linux-v6.1/include/uapi/linux/ |
| D | falloc.h | 21 * filesystem block size boundaries, but this boundary may be larger or
22 * smaller depending on the filesystem and/or the configuration of the
23 * filesystem or file.
52 * of the operation. Most will limit operations to filesystem block size
54 * the filesystem and/or the configuration of the filesystem or file.
69 * granularity of the operation. Most will limit operations to filesystem
71 * depending on the filesystem and/or the configuration of the filesystem
|
12345678910>>...55
