| /linux/Documentation/filesystems/ |
| H A 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
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
25 A connection between the filesystem daemon and the kernel. The
26 connection exists until either the daemon dies, or the filesystem is
27 umounted. Note that detaching (or lazy umounting) the filesystem
29 the last reference to the filesystem is released.
[all …]
|
| H A 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 …]
|
| 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
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.
125 number of inodes and blocks in the filesystem and how many are free,
126 how many inodes and blocks are in each block group, when the filesystem
[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
57 Note that security initialisation is done *after* the filesystem is called so
64 The creation and reconfiguration of a superblock is governed by a filesystem
92 These are operations that can be done on a filesystem context (see
100 A pointer to the file_system_type of the filesystem that is being
107 A pointer to the file system's private data. This is where the filesystem
[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 | 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 | 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 | directory-locking.rst | 7 kinds of locks - per-inode (->i_rwsem) and per-filesystem
55 * lock the filesystem
96 and fail the lookup if it is. Then we try to lock the filesystem and the
101 Note that splicing does *not* involve any modification of the filesystem;
104 filesystem lock prevents any changes of tree topology, other than having a
107 the filesystem lock, their relationship will remain unchanged until
114 Multiple-filesystem stuff
118 another filesystem; it may be ecryptfs doing operation in the underlying
119 filesystem, overlayfs doing something to the layers, network filesystem
122 directory operation on this filesystem might involve directory operations
[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)
86 The inode structure contains pointers to the filesystem blocks which contain
106 A directory is a filesystem object and has an inode just like a file.
[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/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"
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 …]
|
| /linux/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.
|
| H A 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/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
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 …]
|
| /linux/Documentation/admin-guide/ |
| H A D | xfs.rst | 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
153 The filesystem will be mounted without running log recovery.
[all …]
|
| H A 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 …]
|
| /linux/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
66 This strategy improves the filesystem's visibility into the size of the
70 of mapping function calls into the filesystem across a larger amount of
130 * **filesystem mapping lock**: This synchronization primitive is
131 internal to the filesystem and must protect the file mapping data
133 The filesystem author must determine how this coordination should
145 This implies that the filesystem must have already allocated space
[all …]
|
| /linux/Documentation/filesystems/nfs/ |
| 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 …]
|
| 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
50 So, for example, you will only be able to reexport a filesystem over
59 filesystem, the second is the length after that nfs export is reexported
80 - If you export a subdirectory of a filesystem (instead of
81 exporting the filesystem root), that also usually adds 4 to 8
84 filesystem identifier that saves 8 bytes.
89 you're unlikely to have trouble using NFSv4 to reexport any filesystem
111 filesystem locally. A reexport server will also not pass them along to
|
| /linux/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/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/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/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,
|
| /linux/fs/gfs2/ |
| H A D | Kconfig | 11 A cluster filesystem.
15 and writes to the block device like a local filesystem, but also uses
17 filesystem consistency is maintained. One of the nifty features of
18 GFS is perfect consistency -- changes made to the filesystem on one
21 To use the GFS2 filesystem in a cluster, you will need to enable
|