| /linux/Documentation/filesystems/fuse/ |
| 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
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 …]
|
| H A D | fuse-passthrough.rst | 10 FUSE (Filesystem in Userspace) passthrough is a feature designed to improve the
18 the backing file on a lower filesystem) with the FUSE kernel module. The kernel
33 1. The FUSE filesystem must be compiled with ``CONFIG_FUSE_PASSTHROUGH``
79 file is still open by the system on behalf of the FUSE filesystem. This
98 Filesystem Stacking and Shutdown Loops
102 filesystem stacking scenarios if unprivileged users could set up passthrough.
103 A FUSE passthrough filesystem might use a backing file that resides:
105 * On the *same* FUSE filesystem.
106 * On another filesystem (like OverlayFS) which itself might have an upper or
107 lower layer that is a FUSE filesystem.
[all …]
|
| /linux/Documentation/filesystems/ |
| 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 | 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 …]
|
| H A 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 of 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 …]
|
| H A 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 …]
|
| 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 | 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 …]
|
| H A 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 …]
|
| H A 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
|
| 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 | 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.
63 must live on a read-write filesystem because they are independently
133 1024 and the minimum of the system page size and the filesystem
152 FS_IOC_ENABLE_VERITY causes the filesystem to build a Merkle tree for
153 the file and persist it to a filesystem-specific location associated
189 - ``ENOTTY``: this type of filesystem does not implement fs-verity
191 support; or the filesystem superblock has not had the 'verity'
192 feature enabled on it; or the filesystem does not support fs-verity
[all …]
|
| H A 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.
180 access. Because of filesystem caching, the wrong key will then be
279 filesystem's inode table, and there didn't appear to be any
315 number, and filesystem UUID. This normally results in all files
[all …]
|
| H A D | befs.rst | 4 BeOS filesystem for Linux
36 This filesystem doesn't have a maintainer.
40 This module implements the native filesystem of BeOS http://www.beincorporated.com/
46 Be, Inc said, "BeOS Filesystem is officially called BFS, not BeFS".
47 But Unixware Boot Filesystem is called bfs, too. And they are already in
49 filesystem is called befs.
81 filesystem (experimental)", or something like that. Enable that option
93 To use the BeOS filesystem, use filesystem type 'befs'.
123 Dominic Giampalo ... Writing "Practical file system design with Be filesystem"
|
| /linux/fs/ext4/ |
| H A D | Kconfig | 3 tristate "The Extended 4 (ext4) filesystem"
11 This is the next generation of the ext3 filesystem.
13 Unlike the change from ext2 filesystem to ext3 filesystem,
16 physical block numbers. The ext4 filesystem also supports delayed
22 The ext4 filesystem supports mounting an ext3 filesystem; while there
25 features in the filesystem using tune2fs, or formatting a new
26 filesystem as an ext4 filesystem initially. Without explicit enabling
27 of ext4 features, the on disk filesystem format stays fully backward
63 labels in the ext4 filesystem.
72 Enables run-time debugging support for the ext4 filesystem.
|
| /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/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 …]
|
| H A D | porting.rst | 11 Porting Your Filesystem
20 There are several reasons to convert a filesystem to iomap:
24 into the filesystem to return a mapping for only that page.
37 4. Lower maintenance overhead for individual filesystem maintainers.
42 filesystem using iomap.
44 How Do I Convert a Filesystem?
48 ``select FS_IOMAP`` to your filesystem's Kconfig option.
50 variety of your filesystem's supported configurations to build a
64 Next, modify the filesystem's ``get_block(create = false)``
96 w/ DIO enabled in earnest on filesystem.
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A 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.
39 device reclaim space freed by the filesystem. This is
59 across the entire filesystem rather than just on directories
68 to create inodes at any location in the filesystem,
86 If ``largeio`` is specified, a filesystem that was created with a
88 in ``st_blksize``. If the filesystem does not have a ``swidth``
127 An XFS filesystem has up to three parts: a data section, a log
158 The filesystem will be mounted without running log recovery.
[all …]
|
| /linux/Documentation/filesystems/caching/ |
| H A 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/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/filesystems/ext4/ |
| 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
341 - Number of KiB written to this filesystem over its lifetime.
537 The filesystem creator is one of the following:
571 Note that ``EXT4_DYNAMIC_REV`` refers to a revision 1 or newer filesystem.
[all …]
|
| 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.
|
| /linux/fs/fuse/ |
| H A D | Kconfig | 3 tristate "FUSE (Filesystem in Userspace) support"
7 With FUSE it is possible to implement a fully functional filesystem
20 a filesystem based on FUSE, answer Y or M.
33 tristate "Virtio Filesystem"
37 The Virtio Filesystem allows guests to mount file systems from the
44 bool "Virtio Filesystem Direct Host Memory Access support"
54 If you want to allow mounting a Virtio Filesystem with the "dax"
|
| /linux/include/uapi/linux/ |
| H A D | falloc.h | 22 * filesystem block size boundaries, but this boundary may be larger or
23 * smaller depending on the filesystem and/or the configuration of the
24 * filesystem or file.
53 * of the operation. Most will limit operations to filesystem block size
55 * the filesystem and/or the configuration of the filesystem or file.
70 * granularity of the operation. Most will limit operations to filesystem
72 * depending on the filesystem and/or the configuration of the filesystem
|