Lines Matching +full:i +full:- +full:cache +full:- +full:block +full:- +full:size
1 .. SPDX-License-Identifier: GPL-2.0
9 (64 bit) in keeping with increasing disk capacities and state-of-the-art
12 Mailing list: linux-ext4@vger.kernel.org
23 - The latest version of e2fsprogs can be found at:
35 - Create a new filesystem using the ext4 filesystem type:
37 # mke2fs -t ext4 /dev/hda1
41 # tune2fs -O extents /dev/hda1
46 # tune2fs -I 256 /dev/hda1
48 - Mounting:
50 # mount -t ext4 /dev/hda1 /wherever
52 - When comparing performance with other filesystems, it's always
59 '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
61 it is often worthwhile to try changing the data journaling mode; '-o
67 metadata-intensive workloads.
73 -------------------
77 * extent format more robust in face of on-disk corruption due to magics,
79 * improved file allocation (multi-block alloc)
89 * inode allocation using large virtual block groups via flex_bg
91 * large block (up to pagesize) support
94 * Case-insensitive file name lookups
96 [1] Filesystems with a block size of 1k may see a limit imposed by the
99 case-insensitive file name lookups
102 The case-insensitive file name lookup feature is supported on a
103 per-directory basis, allowing the user to mix case-insensitive and
104 case-sensitive directories in the same filesystem. It is enabled by
106 case-insensitive string match operation is only defined when we know how
108 case-insensitive directories, the filesystem must have the
109 casefold feature, which stores the filesystem-wide encoding
111 Unicode (12.1.0, by the time of this writing), encoded in the UTF-8
116 The case-awareness is name-preserving on the disk, meaning that the file
117 name provided by userspace is a byte-per-byte match to what is actually
121 used on large case-insensitive directories with DX feature. On DX
134 operate on that file, but the case-insensitive lookups won't work.
154 Commit block can be written to disk without waiting for descriptor
189 for data-safety. Setting it to 0 will have the same effect as leaving
198 proper on-disk ordering of journal commits, making volatile disk write
200 battery-backed in one way or another, disabling barriers may safely
207 that ext4's inode table readahead algorithm will pre-read into the
208 buffer cache. The default value is 32 blocks.
234 errors=remount-ro
235 Remount the filesystem read-only on an error.
270 documentation in the quota-tools package for more details
276 the above quota options. See documentation in the quota-tools package
281 size and alignment. For RAID5/6 systems this should be the number of
282 data disks * RAID chunk size in file system blocks.
285 Defer block allocation until just before ext4 writes out the block(s)
291 copied from userspace to the page cache, either via the write(2) system
299 a wait for the I/O complete, it doesn't cost much, and can be a huge
314 parameter may improve the throughput of multi-threaded, synchronous
318 The I/O priority (from 0 to 7, where 0 is the highest priority) which
319 should be used for I/O operations submitted by kjournald2 during a
321 priority than the default I/O priority.
328 will detect the replace-via-rename and replace-via-truncate patterns
333 ext3, and avoids the "zero-length" problem that can happen when a
345 it took to zero out the previous block group's inode table. This
351 underlying block device when blocks are freed. This is useful for SSD
352 devices and sparse/thinly-provisioned LUNs, but it is off by default
356 Disables 32-bit UIDs and GIDs. This is for interoperability with
357 older kernels which only store and expect 16-bit values.
360 These options enable or disable the in-kernel facility for tracking
362 allows multi- block allocator and other routines to notice bugs or
374 used for extent-based files. Because of the restrictions this options
378 This limits the size of directories so that any attempt to expand them
386 Enable 64-bit inode version support. This option is off by default.
389 Use direct access (no page cache). See
401 mode - metadata journaling. A crash+recovery can cause incorrect data to
429 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
430 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
436 details of multiblock allocator buddy cache of free blocks
443 /sys/fs/ext4 based on its device name (i.e., /sys/fs/ext4/hdc or
444 /sys/fs/ext4/dm-0). The files in each per-device directory are shown
449 (see also Documentation/ABI/testing/sysfs-fs-ext4)
452 This file is read-only and shows the number of blocks that are dirty in
453 the page cache, but which do not have their location in the filesystem
457 Tuning parameter which (if non-zero) controls the goal inode used by
464 blocks that ext4's inode table readahead algorithm will pre-read into
465 the buffer cache.
468 This file is read-only and shows the number of kilobytes of data that
477 multiple of this tuning parameter if the stripe size is not set in the
489 Tuning parameter which controls the minimum size for requests (as a
490 power of 2) where the buddy cache is used.
499 their blocks allocated out of a block group specific preallocation
505 This file is read-only and shows the number of kilobytes of data that
548 to resize filesystem to the end of the last existing block group,
551 the filesystem new block count.
554 Move the block extents from orig_fd (the one this ioctl is pointing to)
563 block. The new group descriptor is described by ext4_new_group_input
567 block group. Those two ioctls combined is used in userspace online
572 ext3 indirect block mapped inode to ext4 extent mapped inode by walking
573 through indirect block mapping of the original inode and converting
574 contiguous block ranges into ext4 extents of the temporary inode. Then,
582 application-expected ext3 behaviour. Note that this will also start
588 Resize the filesystem to a new size. The number of blocks of resized
609 useful links: http://fedoraproject.org/wiki/ext3-devel