Home
last modified time | relevance | path

Searched refs:is (Results 1 – 25 of 77) sorted by relevance

1234

/fs/cramfs/
DREADME7 a given directory are contiguous, as this is used by readdir).
9 All data is currently in host-endian format; neither mkcramfs nor the
22 Filename. Not generally null-terminated, but it is
25 The order of inode traversal is described as "width-first" (not to be
47 *end* of the i'th <block> (i.e. one past the last byte, which is the
48 same as the start of the (i+1)'th <block> if there is one). The first
52 When the CRAMFS_FLAG_EXT_BLOCK_POINTERS capability bit is set, each
56 The block data is not compressed and should be copied verbatim.
61 aligned to a 4-byte boundary. The block size is either blksize
62 if CRAMFS_BLK_FLAG_UNCOMPRESSED is also specified, otherwise
[all …]
DKconfig7 System). CramFs is designed to be a simple, small, and compressed
8 file system for ROM based embedded systems. CramFs is read-only,
19 This filesystem is limited in capabilities and performance on
20 purpose to remain small and low on RAM usage. It is most suitable
23 which is much better in terms of performance and features.
43 This saves some memory since no intermediate buffering is
46 The location of the CramFs image is determined by a
/fs/overlayfs/
DKconfig8 object in the 'upper' filesystem is visible while the object in the
9 'lower' filesystem is either hidden or, in the case of directories,
18 If this config option is enabled then overlay filesystems will use
19 redirects when renaming directories by default. In this case it is
24 Note, that redirects are not backward compatible. That is, mounting
38 If backward compatibility is not an issue, then it is safe and
49 If this config option is enabled then overlay filesystems will use
51 In this case it is still possible to turn off index globally with the
58 Note, that the inodes index feature is not backward compatible.
59 That is, mounting an overlay which has an inodes index on a kernel
[all …]
/fs/jffs2/
DREADME.Locking6 JFFS2. It is not expected to remain perfectly up to date, but ought to
13 The alloc_sem is a per-filesystem mutex, used primarily to ensure
14 contiguous allocation of space on the medium. It is automatically
24 which they belong. This is for the benefit of NAND flash - adding new
33 the alloc_sem is also used to protect the wbuf-related members of the
35 if the wbuf is currently holding any data is permitted, though.
43 This is the JFFS2-internal equivalent of the inode mutex i->i_sem.
48 The reason that the i_sem itself isn't used for this purpose is to
59 mutex, which is obtained by the garbage collection code and also
74 This is used to serialise access to the eraseblock lists, to the
[all …]
/fs/ntfs/
DKconfig6 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
8 Saying Y or M here enables read support. There is partial, but
16 This is a rewrite from scratch of Linux NTFS support and replaced
18 the Linux 2.4 kernel series is separately available as a patch
28 Linux on your computer it is safe to say N.
40 to insmod when loading the ntfs module. Once the driver is active,
58 The only supported operation is overwriting existing files, without
60 renaming is possible. Note only non-resident files can be written to
66 damaged someones data so we assume it is perfectly safe to use.
68 Note: While write support is safe in this version (a rewrite from
[all …]
/fs/btrfs/
DKconfig19 Btrfs is a general purpose copy-on-write filesystem with extents,
23 The filesystem disk format is no longer unstable, and it's not
25 is a format change, file systems with a unchanged format will
51 writes of the super block). The goal is to verify that the
52 state of the filesystem on disk is always consistent, i.e.,
53 after a power-loss or kernel panic event the filesystem is
56 If the integrity check tool is included and activated in
57 the mount options, plenty of kernel memory is used, and
59 functionality is not intended for normal use.
70 code to make sure it is acting as it should. These are mostly
[all …]
/fs/ext4/
Dinline.c127 struct ext4_xattr_ibody_find is = { in ext4_find_inline_data_nolock() local
139 error = ext4_get_inode_loc(inode, &is.iloc); in ext4_find_inline_data_nolock()
143 error = ext4_xattr_ibody_find(inode, &i, &is); in ext4_find_inline_data_nolock()
147 if (!is.s.not_found) { in ext4_find_inline_data_nolock()
148 if (is.s.here->e_value_inum) { in ext4_find_inline_data_nolock()
154 EXT4_I(inode)->i_inline_off = (u16)((void *)is.s.here - in ext4_find_inline_data_nolock()
155 (void *)ext4_raw_inode(&is.iloc)); in ext4_find_inline_data_nolock()
157 le32_to_cpu(is.s.here->e_value_size); in ext4_find_inline_data_nolock()
161 brelse(is.iloc.bh); in ext4_find_inline_data_nolock()
255 struct ext4_xattr_ibody_find is = { in ext4_create_inline_data() local
[all …]
DKconfig14 This config option is here only for backward compatibility. ext3
15 filesystem is now handled by the ext4 driver.
23 This config option is here only for backward compatibility. ext3
24 filesystem is now handled by the ext4 driver.
31 This config option is here only for backward compatibility. ext3
32 filesystem is now handled by the ext4 driver.
43 This is the next generation of the ext3 filesystem.
46 the on-disk format of ext4 is not forwards compatible with
47 ext3; it is based on extent maps and it supports 48-bit
/fs/xfs/
DKconfig9 XFS is a high performance journaling filesystem which originated
10 on the SGI IRIX platform. It is completely multi-threaded, can
12 variable block sizes, is extent based, and makes extensive use of
17 for complete details. This implementation is on-disk compatible
22 system of your root partition is compiled as a module, you'll need
34 quota is also compatible with the IRIX version of XFS, allowing a
58 which contain a realtime subvolume. The realtime subvolume is a
59 separate area of disk space where only file data is stored. It was
61 for media streaming applications, but is also useful as a generic
77 mounted XFS filesystem. This feature is intended to reduce
[all …]
/fs/affs/
DChanges11 in readdir()) gives compiler warnings but is
24 - When a file is truncated to a size that is not
26 last allocated block is not cleared. Well,
113 partially used last block when a file is truncated.
114 It also marks the inode dirty now (which is not
138 - One set of dentry callbacks is enough. (BH)
144 - The original blocksize of the device is
145 restored when the fs is unmounted. (BH)
209 is that unlink(), rename() and rmdir() have to
210 be smart about them, but the result is worth the
[all …]
/fs/befs/
DChangeLog34 This is bad, since 2.4.9 is still the current RedHat kernel. I added
51 finding the first key that is a substring of the string it is searching
63 * Makefile fix for independent module when CONFIG_MODVERSION is set in
96 * Make directory lookup/read use the NLS if an iocharset is provided. [WD]
102 The option is, simply enough, 'debug'.
111 node. This is the cleaner solution to Brent Miszalaski's problem. [WD]
150 * Anton also told me that the blocksize is not allowed to be larger than
151 the page size in linux, which is 4k i386. Oops. Added a test for
153 practically means is that 8k blocksize volumes won't work without a major
167 superblock type, rather than struct super_block. This is for
[all …]
/fs/reiserfs/
DREADME3 ReiserFS is hereby licensed under the GNU General
17 licensing is governed by the statement in this file, you accept this.
18 It will be a kindness if you identify whether Hans Reiser is allowed
20 under the GPL, because he wants to know if it is okay to do so and put
39 If you have doubts about how to properly do that, or about what is
45 Reiserfs is a file system based on balanced tree algorithms, which is
53 Linux provider put them. There is some disagreement about how useful
54 it is for users to get their fsck and mkreiserfs out of sync with the
55 version of reiserfs that is in their kernel, with many important
58 reiserfs, this is a common source of confusion. Note that some of the
[all …]
/fs/verity/
DKconfig6 # SHA-256 is selected as it's intended to be the default hash algorithm.
10 This option enables fs-verity. fs-verity is the dm-verity
16 Merkle tree. The file is also made read-only.
25 fs-verity is especially useful on large files where not all
27 data each time it is paged back in, which provides better
49 This is meant as a relatively simple mechanism that can be
52 need to check that the verity bit is set in order to get an
/fs/ubifs/
DKconfig17 UBIFS is a file system for flash devices which works on top of UBI.
34 LZO compressor is generally faster than zlib but compresses worse.
41 Zlib compresses better than LZO but it is slower. Say 'Y' if unsure.
48 ZSTD compresses is a big win in speed over Zlib and
56 increased flash wear. This option adds atime support and it is disabled by default
60 so be careful. How often atime is updated depends on the selected strategy:
61 strictatime is the "heavy", relatime is "lighter", etc.
/fs/ocfs2/
DKconfig11 OCFS2 is a general purpose extent based shared disk cluster file
34 O2CB is limited to maintaining a cluster for OCFS2 file systems.
37 It is always safe to say Y here, as the clustering method is
49 It is safe to say Y, as the clustering method is run-time
76 this option for debugging only as it is likely to decrease
/fs/configfs/
DKconfig6 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
12 same system. One is not a replacement for the other.
/fs/isofs/
DKconfig5 This is the standard file system used on CD-ROMs. It was previously
6 known as "High Sierra File System" and is called "hsfs" on other
23 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
24 which allows for long filenames in unicode format (unicode is the
35 This is a Linux-specific extension to RockRidge which lets you store
37 decompressed when the CD-ROM is accessed. See
/fs/freevxfs/
DKconfig6 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
7 file system format. VERITAS VxFS(TM) is the standard file system
13 Currently only readonly access is supported and VxFX versions
17 fstab(5) is 'vxfs' as it describes the file system format, not
20 There is a userspace utility for HP-UX logical volumes which makes
/fs/autofs/
DKconfig7 new name of the autofs Kconfig option. All it does is select
17 The automounter is a tool to automatically mount remote file systems
18 on demand. This implementation is partially kernel-based to reduce
19 overhead in the already-mounted case; this is unlike the BSD
20 automounter (amd), which is a pure user space daemon.
/fs/gfs2/
DKconfig13 that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads
16 filesystem consistency is maintained. One of the nifty features of
17 GFS is perfect consistency -- changes made to the filesystem on one
24 The "nolock" lock module is now built in to GFS2 by default. If
35 interface between GFS2 and the DLM, which is required to use GFS2
/fs/udf/
DKconfig7 This is a file system used on some CD-ROMs and DVDs. Since the
8 file system is supported by multiple operating systems and is more
9 compatible with standard unix file systems, it is also suitable for
/fs/jbd2/
DKconfig8 This is a generic journaling layer for block devices that support
9 both 32-bit and 64-bit block numbers. It is currently used by
28 allows you to enable debugging output while the system is running,
33 with "echo N > /sys/module/jbd2/parameters/jbd2_debug", where N is a
35 output is generated. To turn debugging off again, do
/fs/squashfs/
DKconfig7 Read-Only File System). Squashfs is a highly compressed read-only
16 Squashfs is intended for general read-only filesystem use, for
18 embedded systems where low overhead is needed. Further information
97 decompression is load-balanced across the cores.
117 ZLIB compression is the standard compression used by Squashfs
130 compressed with LZ4 compression. LZ4 compression is mainly
134 LZ4 is not the standard compression used in Squashfs and so most
145 compressed with LZO compression. LZO compression is mainly
149 LZO is not the standard compression used in Squashfs and so most
164 XZ is not the standard compression used in Squashfs and so most
[all …]
/fs/notify/fanotify/
DKconfig8 Say Y here to enable fanotify support. fanotify is a file access
21 Say Y here is you want fanotify listeners to be able to make permissions
22 decisions concerning filesystem events. This is used by some fanotify
24 use those files. This is used by some anti-malware vendors and by some
/fs/bfs/
DKconfig6 Boot File System (BFS) is a file system used under SCO UnixWare to
8 files during the boot process. It is usually mounted under /stand
13 file system is contained in the file
16 If you don't know what this is about, say N.

1234